1. 28 12月, 2012 1 次提交
  2. 21 12月, 2012 1 次提交
  3. 14 8月, 2012 1 次提交
  4. 10 8月, 2012 1 次提交
  5. 19 6月, 2012 1 次提交
  6. 12 6月, 2012 1 次提交
  7. 15 5月, 2012 8 次提交
  8. 14 5月, 2012 1 次提交
    • H
      [media] v4l2-dev: add flag to have the core lock all file operations · 5126f259
      Hans Verkuil 提交于
      This used to be the default if the lock pointer was set, but now that lock is by
      default only used for ioctl serialization. Those drivers that already used
      core locking have this flag set explicitly, except for some drivers where
      it was obvious that there was no need to serialize any file operations other
      than ioctl.
      
      The drivers that didn't need this flag were:
      
      drivers/media/radio/dsbr100.c
      drivers/media/radio/radio-isa.c
      drivers/media/radio/radio-keene.c
      drivers/media/radio/radio-miropcm20.c
      drivers/media/radio/radio-mr800.c
      drivers/media/radio/radio-tea5764.c
      drivers/media/radio/radio-timb.c
      drivers/media/video/vivi.c
      sound/i2c/other/tea575x-tuner.c
      
      The other drivers that use core locking and where it was not immediately
      obvious that this flag wasn't needed were changed so that the flag is set
      together with a comment that that driver needs work to avoid having to
      set that flag. This will often involve taking the core lock in the fops
      themselves.
      
      Eventually this flag should go and it should not be used in new drivers.
      
      There are a few reasons why we want to avoid core locking of non-ioctl
      fops: in the case of mmap this can lead to a deadlock in rare situations
      since when mmap is called the mmap_sem is held and it is possible for
      other parts of the code to take that lock as well (copy_from_user()/copy_to_user()
      perform a down_read(&mm->mmap_sem) when a page fault occurs).
      
      It is very unlikely that that happens since the core lock serializes all
      fops, but the kernel warns about it if lock validation is turned on.
      
      For poll it is also undesirable to take the core lock as that can introduce
      increased latency. The same is true for read/write.
      
      While it was possible to make flags or something to turn on/off taking the
      core lock for each file operation, in practice it is much simpler to just
      not take it at all except for ioctl and leave it to the driver to take the
      lock. There are only a handful fops compared to the zillion ioctls we have.
      
      I also wanted to make it obvious which drivers still take the lock for all
      fops, so that's why I chose to have drivers set it explicitly.
      Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
      Acked-by: NHans de Goede <hdegoede@redhat.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      5126f259
  9. 01 11月, 2011 1 次提交
  10. 04 9月, 2011 1 次提交
  11. 19 1月, 2011 1 次提交
  12. 21 10月, 2010 1 次提交
  13. 03 8月, 2010 1 次提交
  14. 07 5月, 2010 1 次提交
    • H
      V4L/DVB: saa7146: fix regression of the av7110/budget-av driver · 03b1930e
      Hans Verkuil 提交于
      An earlier regression fix for the mxb driver (V4L/DVB: saa7146_vv: fix
      regression where v4l2_device was registered too late) caused a new
      regression in the av7110 driver.
      
      Reverted the old fix and fixed the problem in the mxb driver instead.
      Tested on mxb and budget-av cards.
      
      The real problem is that the saa7146 framework has separate probe()
      and attach() driver callbacks which should be rolled into one. This
      is now done for the mxb driver, but others should do the same. Lack
      of hardware makes this hard to do, though. I hope to get hold of some
      hexium cards and then I can try to improve the framework to prevent
      this from happening again.
      Signed-off-by: NHans Verkuil <hverkuil@xs4all.nl>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      03b1930e
  15. 27 2月, 2010 1 次提交
  16. 16 12月, 2009 4 次提交
  17. 30 3月, 2009 3 次提交
  18. 03 1月, 2009 2 次提交
  19. 30 12月, 2008 1 次提交
  20. 22 10月, 2008 1 次提交
    • H
      V4L/DVB (9327): v4l: use video_device.num instead of minor in video%d · c6330fb8
      Hans Verkuil 提交于
      The kernel number of a v4l2 node (e.g. videoX, radioX or vbiX) is now
      independent of the minor number. So instead of using the minor field
      of the video_device struct one has to use the num field: this always
      contains the kernel number of the device node.
      
      I forgot about this when I did the v4l2 core change, so this patch
      converts all drivers that use it in one go. Luckily the change is
      trivial.
      
      Cc: michael@mihu.de
      Cc: mchehab@infradead.org
      Cc: corbet@lwn.net
      Cc: luca.risolia@studio.unibo.it
      Cc: isely@pobox.com
      Cc: pe1rxq@amsat.org
      Cc: royale@zerezo.com
      Cc: mkrufky@linuxtv.org
      Cc: stoth@linuxtv.org
      Signed-off-by: NHans Verkuil <hverkuil@xs4all.nl>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      c6330fb8
  21. 12 10月, 2008 1 次提交
  22. 27 7月, 2008 1 次提交
  23. 31 3月, 2008 1 次提交
  24. 26 1月, 2008 2 次提交
  25. 10 10月, 2007 1 次提交
  26. 09 5月, 2007 1 次提交