1. 20 6月, 2017 1 次提交
    • R
      [media] media: platform: rcar_drif: Add DRIF support · 7625ee98
      Ramesh Shanmugasundaram 提交于
      This patch adds Digital Radio Interface (DRIF) support to R-Car Gen3 SoCs.
      The driver exposes each instance of DRIF as a V4L2 SDR device. A DRIF
      device represents a channel and each channel can have one or two
      sub-channels respectively depending on the target board.
      
      DRIF supports only Rx functionality. It receives samples from a RF
      frontend tuner chip it is interfaced with. The combination of DRIF and the
      tuner device, which is registered as a sub-device, determines the receive
      sample rate and format.
      
      In order to be compliant as a V4L2 SDR device, DRIF needs to bind with
      the tuner device, which can be provided by a third party vendor. DRIF acts
      as a slave device and the tuner device acts as a master transmitting the
      samples. The driver allows asynchronous binding of a tuner device that
      is registered as a v4l2 sub-device. The driver can learn about the tuner
      it is interfaced with based on port endpoint properties of the device in
      device tree. The V4L2 SDR device inherits the controls exposed by the
      tuner device.
      
      The device can also be configured to use either one or both of the data
      pins at runtime based on the master (tuner) configuration.
      Signed-off-by: NRamesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>
      Signed-off-by: NHans Verkuil <hansverk@cisco.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>
      7625ee98
  2. 14 6月, 2017 1 次提交
  3. 06 6月, 2017 2 次提交
  4. 05 6月, 2017 2 次提交
  5. 19 4月, 2017 1 次提交
    • H
      [media] cec: Kconfig cleanup · 56a263aa
      Hans Verkuil 提交于
      The Kconfig options for the CEC subsystem were a bit messy. In
      addition there were two cec sources (cec-edid.c and cec-notifier.c)
      that were outside of the media/cec directory, which was weird.
      
      Move those sources to media/cec as well.
      
      The cec-edid and cec-notifier functionality is now part of the cec
      module and these are no longer separate modules.
      
      Also remove the MEDIA_CEC_EDID config option and include it with the
      main CEC config option (which defined CEC_EDID anyway).
      
      Added static inlines to cec-edid.h for dummy functions when CEC_CORE
      isn't defined.
      
      CEC drivers should now depend on CEC_CORE.
      
      CEC drivers that need the cec-notifier functionality must explicitly
      select CEC_NOTIFIER.
      
      The s5p-cec and stih-cec drivers depended on VIDEO_DEV instead of
      CEC_CORE, fix that as well.
      Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
      Acked-by: NBenjamin Gaignard <benjamin.gaignard@linaro.org>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>
      56a263aa
  6. 15 4月, 2017 2 次提交
  7. 11 4月, 2017 1 次提交
  8. 10 4月, 2017 1 次提交
  9. 22 3月, 2017 1 次提交
  10. 03 3月, 2017 1 次提交
  11. 08 2月, 2017 3 次提交
  12. 31 1月, 2017 2 次提交
  13. 25 11月, 2016 1 次提交
    • A
      [media] v4l: rcar_fdp1: add FCP dependency · 1d389714
      Arnd Bergmann 提交于
      Commit 4710b752 ("[media] v4l: Add Renesas R-Car FDP1 Driver") in the
      v4l-dvb tree adds CONFIG_VIDEO_RENESAS_FDP1.
      
      It calls into the FCP driver, but when there is no dependency, FCP might
      be a module while FDP1 is built-in.
      
      We have the same logic in VIDEO_RENESAS_VSP1, which also depends on
      FCP not being a module when it is built-in itself.
      
      drivers/media/platform/rcar_fdp1.o: In function `fdp1_pm_runtime_resume':
      rcar_fdp1.c:(.text.fdp1_pm_runtime_resume+0x78): undefined reference to `rcar_fcp_enable'
      drivers/media/platform/rcar_fdp1.o: In function `fdp1_pm_runtime_suspend':
      rcar_fdp1.c:(.text.fdp1_pm_runtime_suspend+0x14): undefined reference to `rcar_fcp_disable'
      drivers/media/platform/rcar_fdp1.o: In function `fdp1_probe':
      rcar_fdp1.c:(.text.fdp1_probe+0x15c): undefined reference to `rcar_fcp_get'
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>
      1d389714
  14. 22 11月, 2016 3 次提交
  15. 17 11月, 2016 2 次提交
  16. 25 10月, 2016 1 次提交
    • A
      [media] platform: pxa_camera: add VIDEO_V4L2 dependency · ff681022
      Arnd Bergmann 提交于
      Moving the pxa_camera driver from soc_camera lots the implied
      VIDEO_V4L2 Kconfig dependency, and building the driver without
      V4L2 results in a kernel that cannot link:
      
      drivers/media/platform/pxa_camera.o: In function `pxa_camera_remove':
      pxa_camera.c:(.text.pxa_camera_remove+0x10): undefined reference to `v4l2_clk_unregister'
      pxa_camera.c:(.text.pxa_camera_remove+0x18): undefined reference to `v4l2_device_unregister'
      drivers/media/platform/pxa_camera.o: In function `pxa_camera_probe':
      pxa_camera.c:(.text.pxa_camera_probe+0x458): undefined reference to `v4l2_of_parse_endpoint'
      drivers/media/v4l2-core/videobuf2-core.o: In function `__enqueue_in_driver':
      drivers/media/v4l2-core/videobuf2-core.o: In function `vb2_core_streamon':
      videobuf2-core.c:(.text.vb2_core_streamon+0x1b4): undefined reference to `v4l_vb2q_enable_media_source'
      drivers/media/v4l2-core/videobuf2-v4l2.o: In function `vb2_ioctl_reqbufs':
      videobuf2-v4l2.c:(.text.vb2_ioctl_reqbufs+0xc): undefined reference to `video_devdata'
      
      This adds back an explicit dependency.
      
      Fixes: 3050b998 ("[media] media: platform: pxa_camera: move pxa_camera out of soc_camera")
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NRobert Jarzmik <robert.jarzmik@free.fr>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>
      ff681022
  17. 21 10月, 2016 1 次提交
  18. 09 9月, 2016 3 次提交
  19. 25 8月, 2016 1 次提交
  20. 24 8月, 2016 1 次提交
  21. 23 8月, 2016 1 次提交
  22. 22 8月, 2016 1 次提交
  23. 14 7月, 2016 1 次提交
    • A
      [media] vsp1: clarify FCP dependency · 19994673
      Arnd Bergmann 提交于
      The newly added FCP support in the vsp1 driver causes a link error
      when CONFIG_RENESAS_FCP=m, since it's not reachable by built-in code:
      
      drivers/media/built-in.o: In function `vsp1_remove':
      :(.text+0xdeca0): undefined reference to `rcar_fcp_put'
      drivers/media/built-in.o: In function `vsp1_probe':
      :(.text+0xdef44): undefined reference to `rcar_fcp_get'
      
      We already have a conditional dependency on FCP that requires
      it for ARM64, so for all others we just have to prevent setting
      RENESAS_VSP1=y when RENESAS_FCP=m by extending the FCP dependency.
      
      Fixes: 94fcdf82 ("[media] v4l: vsp1: Add FCP support")
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>
      19994673
  24. 09 7月, 2016 3 次提交
  25. 28 6月, 2016 2 次提交
  26. 17 6月, 2016 1 次提交