1. 11 1月, 2012 1 次提交
  2. 20 12月, 2011 1 次提交
  3. 08 11月, 2011 8 次提交
  4. 04 11月, 2011 1 次提交
  5. 03 11月, 2011 1 次提交
  6. 08 10月, 2011 1 次提交
  7. 23 9月, 2011 1 次提交
  8. 22 9月, 2011 3 次提交
  9. 14 9月, 2011 1 次提交
    • J
      iommu/omap: Fix build error with !IOMMU_SUPPORT · 7b6d45f1
      Joerg Roedel 提交于
      Without this patch it is possible to select the VIDEO_OMAP3
      driver which then selects OMAP_IOVMM. But the omap iommu
      driver is not compiled without IOMMU_SUPPORT enabled. Fix
      that by forcing OMAP_IOMMU and OMAP_IOVMM are enabled before
      VIDEO_OMAP3 can be selected.
      
      Cc: Ohad Ben-Cohen <ohad@wizery.com>
      Cc: iommu@lists.linux-foundation.org
      Cc: linux-kernel@vger.kernel.org
      Signed-off-by: NJoerg Roedel <joerg.roedel@amd.com>
      7b6d45f1
  10. 11 9月, 2011 1 次提交
  11. 07 9月, 2011 2 次提交
    • S
      [media] s5p-fimc: Add the media device driver · d3953223
      Sylwester Nawrocki 提交于
      Add a top level media device driver aggregating FIMC video devnodes,
      MIPI-CSIS and sensor subdevs. This driver gathers all media entities
      and creates the possible links between them during initialization. By
      default some links will be activated to enable access to all available
      sensors in the system. For example if there are sensors S0, S1 listed
      in the media device platform data definition they will be by default
      assigned to FIMC0, FIMC1 respectively, which in turn will corresponds
      to separate /dev/video?.
      There is enough FIMC H/W entities to cover all available physical camera
      interfaces in the system.
      
      The fimc media device driver is bound to the "s5p-fimc-md" platform device.
      Such platform device should be created by board initialization code
      and camera sensors description array need to be specified as its
      platform data.
      
      The media device driver also implements various video pipeline operations,
      for enabling subdevs power, streaming, etc., which will be used by the
      capture video node driver.
      Signed-off-by: NSylwester Nawrocki <s.nawrocki@samsung.com>
      Signed-off-by: NKyungmin Park <kyungmin.park@samsung.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      d3953223
    • S
      [media] s5p-fimc: Add runtime PM support in the mem-to-mem driver · e9e21083
      Sylwester Nawrocki 提交于
      Add runtime PM and system sleep support in the memory-to-memory
      driver. It's required to enable the FIMC operation on Exynos4
      SoCs. This patch prevents system boot failure when the driver
      is compiled in, as it now tries to access its I/O memory without
      first enabling the corresponding power domain.
      
      The camera capture device suspend/resume is not fully covered,
      the capture device is just powered on/off during the video
      node open/close. However this enables it's normal operation
      on Exynos4 SoCs.
      
      [mchehab@redhat.com: fix a small checkpatch error]
      Signed-off-by: NSylwester Nawrocki <s.nawrocki@samsung.com>
      Signed-off-by: NKyungmin Park <kyungmin.park@samsung.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      e9e21083
  12. 26 8月, 2011 1 次提交
  13. 28 7月, 2011 6 次提交
  14. 26 5月, 2011 1 次提交
  15. 25 5月, 2011 2 次提交
  16. 21 5月, 2011 1 次提交
  17. 20 5月, 2011 4 次提交
  18. 13 4月, 2011 1 次提交
  19. 22 3月, 2011 3 次提交