Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 20 4月, 2012 1 次提交
  3. 09 4月, 2012 1 次提交
  5. 08 3月, 2012 1 次提交
  7. 15 2月, 2012 1 次提交
    • H
      [media] v4l2: standardize log start/end message · e2ecb257
      由 Hans Verkuil 提交于 
      For drivers that properly use the v4l2 framework (i.e. set v4l2_dev in the
video_device struct), the start and end messages of VIDIOC_LOG_STATUS are
now generated automatically. People tended to forget these, but the v4l2-ctl
tool scans for these messages, and it also makes it easier to read the status
output in the kernel log.

The cx18, ivtv and bttv drivers were changed since they no longer need to
log these start/end messages.

In saa7164 two empty log_status functions were removed.

Also added a helper function to v4l2-ctrl.c that can be used as the
vidioc_log_status callback if all you need to do is to log the current control
values. This is now used by pwc and vivi.
Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
Cc: Steven Toth <stoth@kernellabs.com>
Cc: Andy Walls <awalls@md.metrocast.net>
Cc: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      e2ecb257
  9. 14 2月, 2012 3 次提交
  11. 24 1月, 2012 1 次提交
  13. 16 1月, 2012 1 次提交
  15. 07 9月, 2011 1 次提交
  17. 28 7月, 2011 3 次提交
    • H
      [media] v4l2-event/ctrls/fh: allocate events per fh and per type instead of just per-fh · f1e393de
      由 Hans Verkuil 提交于 
      The driver had to decide how many events to allocate when the v4l2_fh struct
was created. It was possible to add more events afterwards, but there was no
way to ensure that you wouldn't miss important events if the event queue
would fill up for that filehandle.

In addition, once there were no more free events, any new events were simply
dropped on the floor.

For the control event in particular this made life very difficult since
control status/value changes could just be missed if the number of allocated
events and the speed at which the application read events was too low to keep
up with the number of generated events. The application would have no idea
what the latest state was for a control since it could have missed the latest
control change.

So this patch makes some major changes in how events are allocated. Instead
of allocating events per-filehandle they are now allocated when subscribing an
event. So for that particular event type N events (determined by the driver)
are allocated. Those events are reserved for that particular event type.
This ensures that you will not miss events for a particular type altogether.

In addition, if there are N events in use and a new event is raised, then
the oldest event is dropped and the new one is added. So the latest event
is always available.

This can be further improved by adding the ability to merge the state of
two events together, ensuring that no data is lost at all. This will be
added in the next patch.

This also makes it possible to allow the user to determine the number of
events that will be allocated. This is not implemented at the moment, but
would be trivial.
Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      f1e393de
    • H
      [media] ivtv: add control event support · 5138870d
      由 Hans Verkuil 提交于 
      Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      5138870d
    • M
      [media] ivtv,cx18: Use default version control for VIDIOC_QUERYCAP · 3c2d464e
      由 Mauro Carvalho Chehab 提交于 
      After discussing with Andy Walls on irc, we've agreed that this
is the best thing to do. No regressions will be introduced, as 3.x.y
is greater then the current versions for cx18 and ivtv.
Acked-by: NHans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      3c2d464e
  19. 08 7月, 2011 1 次提交
  21. 01 6月, 2011 1 次提交
  23. 23 3月, 2011 3 次提交
  25. 21 10月, 2010 1 次提交
  27. 09 8月, 2010 1 次提交
  29. 01 6月, 2010 1 次提交
  31. 19 5月, 2010 5 次提交
  33. 18 5月, 2010 2 次提交
  35. 17 6月, 2009 1 次提交
  37. 10 5月, 2009 1 次提交
  39. 07 4月, 2009 3 次提交
  41. 30 3月, 2009 2 次提交
  43. 17 2月, 2009 2 次提交
  45. 03 1月, 2009 3 次提交