Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 09 7月, 2016 1 次提交
  3. 01 10月, 2015 1 次提交
  5. 30 1月, 2015 1 次提交
  7. 08 9月, 2014 1 次提交
  9. 17 7月, 2014 1 次提交
    • L
      [media] v4l: Support extending the v4l2_pix_format structure · d52e2381
      由 Laurent Pinchart 提交于 
      The v4l2_pix_format structure has no reserved field. It is embedded in
the v4l2_framebuffer structure which has no reserved fields either, and
in the v4l2_format structure which has reserved fields that were not
previously required to be zeroed out by applications.

To allow extending v4l2_pix_format, inline it in the v4l2_framebuffer
structure, and use the priv field as a magic value to indicate that the
application has set all v4l2_pix_format extended fields and zeroed all
reserved fields following the v4l2_pix_format field in the v4l2_format
structure.

The availability of this API extension is reported to userspace through
the new V4L2_CAP_EXT_PIX_FORMAT capability flag. Just checking that the
priv field is still set to the magic value at [GS]_FMT return wouldn't
be enough, as older kernels don't zero the priv field on return.

To simplify the internal API towards drivers zero the extended fields
and set the priv field to the magic value for applications not aware of
the extensions.
Signed-off-by: NLaurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Signed-off-by: NMauro Carvalho Chehab <m.chehab@samsung.com>
      d52e2381
  11. 05 7月, 2014 2 次提交
  13. 26 9月, 2013 2 次提交
  15. 21 8月, 2013 1 次提交
  17. 17 6月, 2013 1 次提交
  19. 24 3月, 2013 1 次提交
  21. 23 3月, 2013 1 次提交
  23. 06 3月, 2013 2 次提交
  25. 06 2月, 2013 1 次提交
  27. 28 10月, 2012 1 次提交
  29. 26 9月, 2012 1 次提交
  31. 14 9月, 2012 2 次提交
    • H
      [media] gspca: Fix input urb creation / destruction surrounding suspend resume · 36adfca9
      由 Hans de Goede 提交于 
      1) We always re-create the input-urb on resume, so we must also always
   destroy it on suspend to avoid leaking it
2) If we're going to do an init_transfer, then that will destroy the urb
   before starting the stream (nop if there is none), and (re-)create it
   once the stream is started. So there is little use in creating it, if
   we're going to do an init_transfer immediately afterward
Signed-off-by: NHans de Goede <hdegoede@redhat.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      36adfca9
    • H
      [media] gspca: Don't set gspca_dev->dev to NULL before stop0 · 345321dc
      由 Hans de Goede 提交于 
      In commit a3d6e8cc gspca_dev->dev is set
to NULL on disconnect, before calling stop0. The plan was to get rid of
gspca_dev->present and instead simply check for gspca_dev->dev everywhere
where we were checking for present. This should be race free since all users
of gspca_dev->dev hold the usb_lock, or so I thought.

But I was wrong, drivers which use a work-queue + synchronous bulk transfers
to get the video data don't hold the usb_lock while doing so, their stop0
callbacks stop the workqueue, so they won't be using gspca_dev->dev anymore
after the stop0 call, but they might be dereferincing it before, so we should
not set gspca_dev->dev to NULL on disconnect before calling stop0.

This also means that the workqueue functions in these drivers cannot
use gspca_dev->dev to check if they need to stop because of disconnection,
so we will need to keep gspca_dev->present around, and set that to 0 on
disconnect, before calling stop0. Unfortunately as part of the plan to remove
gspca_dev->present, these workqueues where already moved over to checking
for gspca_dev->dev instead of gspca_dev->present as part of commit
254902b0, so this patch also reverts those
parts of that commit.
Signed-off-by: NHans de Goede <hdegoede@redhat.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      345321dc
  33. 16 8月, 2012 1 次提交
  35. 31 7月, 2012 3 次提交
  37. 12 6月, 2012 1 次提交
  39. 15 5月, 2012 1 次提交
  41. 14 5月, 2012 12 次提交
  43. 06 1月, 2012 2 次提交