1. 10 6月, 2015 1 次提交
  2. 30 5月, 2015 1 次提交
  3. 03 4月, 2015 1 次提交
  4. 02 2月, 2015 1 次提交
  5. 27 1月, 2015 1 次提交
  6. 23 12月, 2014 1 次提交
  7. 17 12月, 2014 1 次提交
  8. 22 7月, 2014 1 次提交
  9. 29 3月, 2014 1 次提交
  10. 14 3月, 2014 1 次提交
  11. 11 3月, 2014 2 次提交
  12. 07 1月, 2014 1 次提交
  13. 21 12月, 2013 1 次提交
  14. 20 12月, 2013 1 次提交
    • H
      [media] omap24xx/tcm825x: move to staging for future removal · a03636cb
      Hans Verkuil 提交于
      The omap24xx driver and the tcm825x sensor driver are the only two
      remaining drivers to still use the old deprecated v4l2-int-device API.
      
      Nobody maintains these drivers anymore. But unfortunately the v4l2-int-device
      API is used by out-of-tree drivers (MXC platform). This is a very bad situation
      since as long as this deprecated API stays in the kernel there is no reason for
      those out-of-tree drivers to convert.
      
      This patch moves v4l2-int-device and the two drivers that depend on it to
      staging in preparation for their removal.
      
      If someone would be interested in getting these drivers to work, then start with
      this since it's not very far from the state where they used to work:
      
      <URL:http://vihersipuli.retiisi.org.uk/cgi-bin/gitweb.cgi?p=~sailus/linux-omap/.git;a=summary>
      
      The branch is n800-cam. Porting to up-to-date APIs can then be done. David
      might have done some work in that area, so check with him first.
      Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
      Cc: Sakari Ailus <sakari.ailus@iki.fi>
      Cc: David Cohen <dacohen@gmail.com>
      Signed-off-by: NMauro Carvalho Chehab <m.chehab@samsung.com>
      a03636cb
  15. 31 10月, 2013 1 次提交
  16. 14 10月, 2013 1 次提交
  17. 26 8月, 2013 2 次提交
  18. 17 6月, 2013 1 次提交
  19. 13 6月, 2013 1 次提交
  20. 26 4月, 2013 1 次提交
  21. 25 3月, 2013 1 次提交
  22. 24 3月, 2013 5 次提交
  23. 22 3月, 2013 1 次提交
  24. 09 2月, 2013 3 次提交
  25. 06 2月, 2013 2 次提交
  26. 06 1月, 2013 1 次提交
  27. 27 9月, 2012 1 次提交
  28. 26 9月, 2012 1 次提交
  29. 14 9月, 2012 2 次提交
    • H
      [media] ad9389b: driver for the Analog Devices AD9389B video encoder · 117a55b6
      Hans Verkuil 提交于
      Initial version of this driver.
      
      The full datasheets are available from the Analog Devices website:
      
        http://ez.analog.com/docs/DOC-1741
      
      Not all features of the receiver are supported by this driver for various
      reasons. Most notably:
      
      - No CEC support (the CEC API needs a lot more discussion)
      - No HDCP repeater support (we don't use that either)
      
      I'm sure that there are more things missing, but this driver does work
      well for our hardware.
      
      Note that I am using the register addresses instead of register names: the
      datasheet containing the register descriptions is organized by register
      address. Using names would make the datasheet lookup very hard. An attempt
      was made to try and document what is being done when registers are used
      instead.
      Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      117a55b6
    • H
      [media] adv7604: driver for the Analog Devices ADV7604 video decoder · 54450f59
      Hans Verkuil 提交于
      Initial version of this driver.
      
      The full datasheets are available from the Analog Devices website:
      
        http://ez.analog.com/docs/DOC-1545
      
      Not all features of the receiver are supported by this driver for various
      reasons. Most notably:
      
      - No CEC support (the CEC API needs a lot more discussion)
      - Only port A of the four HDMI input ports is implemented (our hardware only
        uses that port)
      - No HDCP repeater support (we don't use that either)
      
      And since there are some 600-odd pages of datasheet for this single device,
      I'm sure that there are many more things missing, but this driver does work
      well for our hardware.
      
      Note that I am using the register addresses instead of register names: the
      datasheet containing the register descriptions is organized by register
      address. Using names would make the datasheet lookup very hard. An attempt
      was made to try and document what is being done when registers are used
      instead.
      Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      54450f59
  30. 21 8月, 2012 1 次提交