1. 13 1月, 2014 1 次提交
  2. 10 12月, 2013 1 次提交
  3. 30 11月, 2013 1 次提交
  4. 17 10月, 2013 2 次提交
  5. 24 8月, 2013 1 次提交
  6. 18 8月, 2013 2 次提交
  7. 09 6月, 2013 1 次提交
  8. 31 3月, 2013 1 次提交
  9. 29 3月, 2013 1 次提交
  10. 24 3月, 2013 2 次提交
    • H
      [media] v4l2-ctrls: add V4L2_CID_MPEG_VIDEO_REPEAT_SEQ_HEADER control · 9ca5470c
      Hans Verkuil 提交于
      Control whether video sequence headers should be repeated.
      Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      9ca5470c
    • A
      [media] v4l2-ctrls: eliminate lockdep false alarms for struct v4l2_ctrl_handler.lock · 6cd247ef
      Andy Walls 提交于
      When calling v4l2_ctrl_add_handler(), lockdep would detect a potential
      recursive locking problem on a situation that is by design intended and
      not a recursive lock.  This happened because all struct
      v4l2_ctrl_handler.lock mutexes were created as members of the same lock
      class in v4l2_ctrl_handler_init(), and v4l2_ctrl_add_handler() takes the
      hdl->lock on two different v4l2_ctrl_handler instances.
      This change breaks the large lockdep lock class for struct
      v4l2_ctrl_handler.lock and breaks it into v4l2_ctrl_handler
      instantiation specific lock classes with meaningful class names.
      This will validly eliminate lockdep alarms for v4l2_ctrl_handler locking
      validation, as long as the relationships between drivers adding v4l2
      controls to their own handler from other v4l2 drivers' control handlers
      remains straightforward.
      struct v4l2_ctrl_handler.lock lock classes are created with names such
      that the output of cat /proc/lockdep indicates where in the v4l2 driver
      code v4l2_ctrl_handle_init() is being called on instantiations:
      ffffffffa045f490 FD:   10 BD:    8 +.+...: cx2341x:1534:(hdl)->lock
      ffffffffa0497d20 FD:   12 BD:    2 +.+.+.: saa7115:1581:(hdl)->lock
      ffffffffa04ac660 FD:   14 BD:    2 +.+.+.: msp3400_driver:756:(hdl)->lock
      ffffffffa0484b90 FD:   12 BD:    1 +.+.+.: ivtv_gpio:366:(&itv->hdl_gpio)->lock
      ffffffffa04eb530 FD:   11 BD:    2 +.+.+.: cx25840_core:1982:(&state->hdl)->lock
      ffffffffa04fbc80 FD:   11 BD:    3 +.+.+.: wm8775:246:(&state->hdl)->lock
      Some lock chains, that were previously causing the recursion alarms, are
      now visible in the output of cat /proc/lockdep_chains:
      irq_context: 0
      [ffffffffa0497d20] saa7115:1581:(hdl)->lock
      [ffffffffa045f490] cx2341x:1534:(hdl)->lock
      irq_context: 0
      [ffffffffa04ac660] msp3400_driver:756:(hdl)->lock
      [ffffffffa045f490] cx2341x:1534:(hdl)->lock
      irq_context: 0
      [ffffffffa0484b90] ivtv_gpio:366:(&itv->hdl_gpio)->lock
      [ffffffffa045f490] cx2341x:1534:(hdl)->lock
      irq_context: 0
      [ffffffffa04eb530] cx25840_core:1982:(&state->hdl)->lock
      [ffffffffa045f490] cx2341x:1534:(hdl)->lock
      irq_context: 0
      [ffffffffa04fbc80] wm8775:246:(&state->hdl)->lock
      [ffffffffa045f490] cx2341x:1534:(hdl)->lock
      Signed-off-by: NAndy Walls <awalls@md.metrocast.net>
      [hans.verkuil@cisco.com: keep mutex_init in v4l2_ctrl_handler_init_class]
      Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      6cd247ef
  11. 06 2月, 2013 3 次提交
  12. 06 1月, 2013 1 次提交
  13. 05 1月, 2013 1 次提交
  14. 06 10月, 2012 3 次提交
  15. 02 10月, 2012 1 次提交
  16. 26 9月, 2012 1 次提交
  17. 14 9月, 2012 2 次提交
  18. 14 8月, 2012 1 次提交
  19. 31 7月, 2012 2 次提交
  20. 15 5月, 2012 12 次提交