1. 02 12月, 2014 1 次提交
  2. 15 11月, 2013 1 次提交
  3. 24 3月, 2013 2 次提交
  4. 25 1月, 2013 1 次提交
    • H
      [media] radio: set vfl_dir correctly to fix modulator regression · ce4a3d52
      Hans Verkuil 提交于
      The vfl_dir field should be set to indicate whether a device can receive
      data, output data or can do both. This is used to let the v4l core know
      which ioctls should be accepted and which can be refused.
      Unfortunately, when this field was added the radio modulator drivers were
      not updated: radio modulators transmit and so vfl_dir should be set to
      VFL_DIR_TX (or VFL_DIR_M2M in the special case of wl128x).
      Because of this omission it is not possible to call g/s_modulator for these
      drivers, which effectively renders them useless.
      This patch sets the correct vfl_dir value for these drivers, correcting
      this bug.
      Thanks to Paul Grinberg for bringing this to my attention.
      Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      ce4a3d52
  5. 04 1月, 2013 1 次提交
    • G
      Drivers: media: remove __dev* attributes. · 4c62e976
      Greg Kroah-Hartman 提交于
      CONFIG_HOTPLUG is going away as an option.  As a result, the __dev*
      markings need to be removed.
      
      This change removes the use of __devinit, __devexit_p, __devinitdata,
      __devinitconst, and __devexit from these drivers.
      
      Based on patches originally written by Bill Pemberton, but redone by me
      in order to handle some of the coding style issues better, by hand.
      
      Cc: Bill Pemberton <wfp5p@virginia.edu>
      Cc: Mauro Carvalho Chehab <mchehab@redhat.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      4c62e976
  6. 28 12月, 2012 1 次提交
  7. 27 9月, 2012 1 次提交
  8. 26 9月, 2012 3 次提交
  9. 14 8月, 2012 1 次提交
  10. 19 6月, 2012 1 次提交
  11. 11 1月, 2012 1 次提交
  12. 01 11月, 2011 1 次提交
  13. 21 9月, 2011 1 次提交
  14. 28 7月, 2011 1 次提交
    • H
      [media] v4l2-ctrls: fix and improve volatile control handling · ddac5c10
      Hans Verkuil 提交于
      If you have a cluster of controls that is a mix of volatile and non-volatile
      controls, then requesting the value of the volatile control would fail if the
      master control of that cluster was non-volatile. The code assumed that the
      volatile state of the master control was the same for all other controls in
      the cluster.
      
      This is now fixed.
      
      In addition, it was clear from bugs in some drivers that it was confusing that
      the ctrl->cur union had to be used in g_volatile_ctrl. Several drivers used the
      'new' values instead. The framework was changed so that drivers now set the new
      value instead of the current value.
      
      This has an additional benefit as well: the volatile values are now only stored
      in the 'new' value, leaving the current value alone. This is useful for
      autofoo/foo control clusters where you want to have a 'foo' control act like a
      volatile control if 'autofoo' is on, but as a normal control when it is off.
      
      Since with this change the cur value is no longer overwritten when g_volatile_ctrl
      is called, you can use it to remember the original 'foo' value. For example:
      
      autofoo = 0, foo = 10 and foo is non-volatile.
      
      Now autofoo is set to 1 and foo is marked volatile. Retrieving the foo value
      will get the volatile value. Set autofoo back to 0, which marks foo as non-
      volatile again, and retrieving foo will get the old current value of 10.
      Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      ddac5c10
  15. 27 5月, 2011 1 次提交
  16. 25 5月, 2011 1 次提交
  17. 23 3月, 2011 1 次提交
  18. 22 3月, 2011 2 次提交
  19. 19 1月, 2011 1 次提交
  20. 29 12月, 2010 2 次提交