1. 14 5月, 2012 2 次提交
    • H
      [media] v4l2-dev/ioctl: determine the valid ioctls upfront · 48ea0be0
      Hans Verkuil 提交于
      Rather than testing whether an ioctl is implemented in the driver or not
      every time the ioctl is called, do it upfront when the device is registered.
      
      This also allows a driver to disable certain ioctls based on the capabilities
      of the detected board, something you can't do today without creating separate
      v4l2_ioctl_ops structs for each new variation.
      
      For the most part it is pretty straightforward, but for control ioctls a flag
      is needed since it is possible that you have per-filehandle controls, and that
      can't be determined upfront of course.
      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>
      48ea0be0
    • H
      [media] v4l2-dev: make it possible to skip locking for selected ioctls · 8ab75e3e
      Hans Verkuil 提交于
      Using the V4L2 core lock is a very robust method that is usually very good
      at doing the right thing. But some drivers, particularly USB drivers, may
      want to prevent the core from taking the lock for specific ioctls, particularly
      buffer queuing ioctls.
      
      The reason is that certain commands like S_CTRL can take a long time to process
      over USB and all the time the core has the lock, preventing VIDIOC_DQBUF from
      proceeding, even though a frame may be ready in the queue.
      
      This introduces unwanted latency.
      
      Since the buffer queuing commands often have their own internal lock it is
      often not necessary to take the core lock. Drivers can now say that they don't
      want the core to take the lock for specific ioctls.
      
      As it is a specific opt-out it makes it clear to the reviewer that those
      ioctls will need more care when reviewing.
      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>
      8ab75e3e
  2. 20 3月, 2012 1 次提交
  3. 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
  4. 14 2月, 2012 1 次提交
  5. 24 1月, 2012 1 次提交
    • H
      [media] V4L2: Add per-device-node capabilities · 583aa3a9
      Hans Verkuil 提交于
      If V4L2_CAP_DEVICE_CAPS is set, then the new device_caps field is filled with
      the capabilities of the opened device node.
      
      The capabilities field traditionally contains the capabilities of the physical
      device, being a superset of all capabilities available at the several device
      nodes. E.g., if you open /dev/video0, then if it contains VBI caps then that means
      that there is a corresponding vbi node as well. And the capabilities field of
      both the video and vbi nodes should contain identical caps.
      
      However, it would be very useful to also have a capabilities field that contains
      just the caps for the currently open device, hence the new CAP bit and field.
      Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      583aa3a9
  6. 16 1月, 2012 1 次提交
  7. 11 1月, 2012 2 次提交
  8. 07 1月, 2012 1 次提交
  9. 04 11月, 2011 1 次提交
  10. 08 10月, 2011 1 次提交
  11. 07 9月, 2011 2 次提交
  12. 31 7月, 2011 1 次提交
  13. 28 7月, 2011 5 次提交
  14. 08 7月, 2011 2 次提交
  15. 31 3月, 2011 1 次提交
  16. 23 3月, 2011 2 次提交
  17. 22 3月, 2011 4 次提交
  18. 19 1月, 2011 1 次提交
  19. 29 12月, 2010 1 次提交
  20. 09 8月, 2010 1 次提交
  21. 19 5月, 2010 5 次提交
  22. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  23. 16 12月, 2009 1 次提交
    • M
      V4L/DVB (13571): v4l: Adding Digital Video Timings APIs · b6456c0c
      Muralidharan Karicheri 提交于
      This adds the above APIs to the v4l2 core. This is based on version v1.2
      of the RFC titled "V4L - Support for video timings at the input/output interface"
      Following new ioctls are added:-
      
              - VIDIOC_ENUM_DV_PRESETS
              - VIDIOC_S_DV_PRESET
              - VIDIOC_G_DV_PRESET
              - VIDIOC_QUERY_DV_PRESET
              - VIDIOC_S_DV_TIMINGS
              - VIDIOC_G_DV_TIMINGS
      
      Please refer to the RFC for the details. This code was tested using vpfe
      capture driver on TI's DM365. Following is the test configuration used :-
      
      Blu-Ray HD DVD source -> TVP7002 -> DM365 (VPFE) ->DDR
      
      A draft version of the TVP7002 driver (currently being reviewed in the mailing
      list) was used that supports V4L2_DV_1080I60 & V4L2_DV_720P60 presets.
      
      A loopback video capture application was used for testing these APIs. This calls
      following IOCTLS :-
      
       -  verify the new v4l2_input capabilities flag added
       -  Enumerate available presets using VIDIOC_ENUM_DV_PRESETS
       -  Set one of the supported preset using VIDIOC_S_DV_PRESET
       -  Get current preset using VIDIOC_G_DV_PRESET
       -  Detect current preset using VIDIOC_QUERY_DV_PRESET
       -  Using stub functions in tvp7002, verify VIDIOC_S_DV_TIMINGS
          and VIDIOC_G_DV_TIMINGS ioctls are received at the sub device.
       -  Tested on 64bit platform by Hans Verkuil
      Signed-off-by: NMuralidharan Karicheri <m-karicheri2@ti.com>
      Signed-off-by: NHans Verkuil <hverkuil@xs4all.nl>
      Reviewed-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      b6456c0c
  24. 12 9月, 2009 1 次提交