1. 29 12月, 2010 5 次提交
  2. 21 10月, 2010 8 次提交
    • J
      [media] Add the via framebuffer camera controller driver · 024fafba
      Jonathan Corbet 提交于
      Add a driver for the video capture port on VIA integrated chipsets.  This
      version has a remaining OLPCism or two and expects to be talking to an
      ov7670; those can be improved as the need arises.
      
      This work was supported by the One Laptop Per Child project.
      Thanks to Laurent Pinchart for a number of useful comments.
      
      Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
      Signed-off-by: NJonathan Corbet <corbet@lwn.net>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      024fafba
    • S
      [media] Add driver for Siliconfile SR030PC30 VGA camera · 3e9c2b84
      Sylwester Nawrocki 提交于
      Add an I2C/v4l2-subdev driver for Siliconfile SR030PC30 VGA
      camera sensor with Image Signal Processor. SR030PC30 is
      the low resolution camera sensor on Samsung Aquila boards.
      Signed-off-by: NSylwester Nawrocki <s.nawrocki@samsung.com>
      Signed-off-by: NKyungmin Park <kyungmin.park@samsung.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      3e9c2b84
    • G
      [media] V4L: add an IMX074 sensor soc-camera / v4l2-subdev driver · 67826235
      Guennadi Liakhovetski 提交于
      This patch adds an initial driver for the IMXъ74 image sensor from Sony.
      Lacking documentation, only very basic functionality in one specific image
      format has been implemented and tested.
      Signed-off-by: NGuennadi Liakhovetski <g.liakhovetski@gmx.de>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      67826235
    • J
      [media] SoC Camera: add driver for OV6650 sensor · 2f6e2404
      Janusz Krzysztofik 提交于
      This patch provides a V4L2 SoC Camera driver for OV6650 camera sensor, found
      on OMAP1 SoC based Amstrad Delta videophone.
      
      Since I have no experience with camera sensors, and the sensor documentation I
      was able to find was not very comprehensive, I left most settings at their
      default (reset) values, except for:
      - those required for proper mediabus parameters and picture geometry and
        format setup,
      - those used by controls.
      Resulting picture quality may be far from perfect, but better than nothing.
      
      In order to be able to get / set the sensor frame rate from userspace, I
      decided to provide two not yet SoC camera supported operations, g_parm and
      s_parm. These can be used after applying patch 4/6 from this series,
      "SoC Camera: add support for g_parm / s_parm operations".
      
      Created and tested against linux-2.6.36-rc5 on Amstrad Delta.
      Signed-off-by: NJanusz Krzysztofik <jkrzyszt@tis.icnet.pl>
      Signed-off-by: NGuennadi Liakhovetski <g.liakhovetski@gmx.de>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      2f6e2404
    • J
      [media] SoC Camera: add driver for OMAP1 camera interface · bdc621fc
      Janusz Krzysztofik 提交于
      This is a V4L2 driver for TI OMAP1 SoC camera interface.
      
      Both videobuf-dma versions are supported, contig and sg, selectable with a
      module option. The former uses less processing power, but often fails to
      allocate contignuous buffer memory. The latter is free of this problem, but
      generates tens of DMA interrupts per frame. If contig memory allocation ever
      fails, the driver falls back to sg automatically on next open, but still can
      be switched back to contig manually. Both paths work stable for me, even
      under heavy load, on my OMAP1510 based Amstrad Delta videophone, that is the
      oldest, least powerfull OMAP1 implementation.
      
      The interface generally works in pass-through mode. Since input data byte
      endianess can be swapped, it provides up to two v4l2 pixel formats per each of
      several soc_mbus formats that have their swapped endian counterparts.
      
      Boards using this driver can provide it with the following platform data:
      - if and what freqency clock is expected by an on-board camera sensor,
      - what is the maximum pixel clock that should be accepted from the sensor,
      - what is the polarity of the sensor provided pixel clock,
      - if the interface GPIO line is connected to a sensor reset/powerdown input
        and what is the input polarity.
      
      Created and tested against linux-2.6.36-rc5 on Amstrad Delta.
      Signed-off-by: NJanusz Krzysztofik <jkrzyszt@tis.icnet.pl>
      Signed-off-by: NGuennadi Liakhovetski <g.liakhovetski@gmx.de>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      bdc621fc
    • M
      V4L/DVB: Deprecate stradis driver · 96322b80
      Mauro Carvalho Chehab 提交于
      The driver author seems to not worked on this driver since its conversion
      from 2.2 to 2.4. Nobody is known to have a stradis hardware for testing. As
      it still uses V4L1 API, BKL and probably some other old stuff, someone would
      need to work on it to preserve the driver. Instead of investing time and
      efforts to keep porting it to work with new API's, it seems better to just
      drop the driver.
      
      So, let's move it to drivers/staging and label it to die at 2.6.38, if nobody
      cares enough to port parallel port support to gspca or to create a new driver
      that uses the same gspca-cpia sub-driver.
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      96322b80
    • M
      V4L/DVB: Deprecate cpia driver (used for parallel port webcams) · 7af97eff
      Mauro Carvalho Chehab 提交于
      cpia driver were re-written inside gspca driver, for USB devices. The only
      functionality that were not migrated is the support for parallel port,
      as:
      	1) the developer didn't find any hardware;
      	2) it doesn't  seem important to keep support for a parallel port webcam,
      	   as this is an obsolete technology;
      	3) the changes at gspca for it to work with parallel port would be very large;
      	4) this driver still uses BKL.
      
      So, let's move it to drivers/staging and label it to die at 2.6.38, if nobody
      cares enough to port parallel port support to gspca or to create a new driver
      that uses the same gspca-cpia sub-driver.
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      7af97eff
    • H
      V4L/DVB: saa5246a/saa5249: Remove obsolete teletext drivers · 563711f1
      Hans Verkuil 提交于
      These old i2c teletext drivers are not supported by any hardware and cannot be
      tested anymore.
      
      Note that while the mxb board seemingly used the saa5246a driver, in reality
      this teletext driver never worked.
      
      These drivers are removed as part of the vtx feature removal, originally
      scheduled for 2.6.35.
      Signed-off-by: NHans Verkuil <hverkuil@xs4all.nl>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      563711f1
  3. 09 8月, 2010 2 次提交
    • H
      V4L/DVB: v4l2: Add new control handling framework · 0996517c
      Hans Verkuil 提交于
      Add a new framework to handle controls which makes life for driver
      developers much easier.
      
      Note that this patch moves some of the control support that used to be in
      v4l2-common.c to v4l2-ctrls.c. The tables were copied unchanged. The body
      of v4l2_ctrl_query_fill() was copied to a new v4l2_ctrl_fill() function
      in v4l2-ctrls.c. This new function doesn't use the v4l2_queryctrl
      struct anymore, which makes it more general.
      
      The remainder of v4l2-ctrls.c is all new. Highlights include:
      
      - No need to implement VIDIOC_QUERYCTRL, QUERYMENU, S_CTRL, G_CTRL,
        S_EXT_CTRLS, G_EXT_CTRLS or TRY_EXT_CTRLS in either bridge drivers
        or subdevs. New wrapper functions are provided that can just be plugged in.
        Once everything has been converted these wrapper functions can be removed as well.
      
      - When subdevices are added their controls can be automatically merged
        with the bridge driver's controls.
      
      - Most drivers just need to implement s_ctrl to set the controls.
        The framework handles the locking and tries to be as 'atomic' as possible.
      
      - Ready for the subdev device nodes: the same mechanism applies to subdevs
        and their device nodes as well. Sub-device drivers can make controls
        local, preventing them from being merged with bridge drivers.
      
      - Takes care of backwards compatibility handling of VIDIOC_S_CTRL and
        VIDIOC_G_CTRL. Handling of V4L2_CID_PRIVATE_BASE is fully transparent.
        CTRL_CLASS controls are automatically added.
      Signed-off-by: NHans Verkuil <hverkuil@xs4all.nl>
      Reviewed-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      0996517c
    • S
      V4L/DVB: v4l: Add driver for Samsung S5P SoC video postprocessor · 5fd8f738
      Sylwester Nawrocki 提交于
      This driver exports a video device node per each camera interface/
      video postprocessor (FIMC) device contained in Samsung S5P SoC series.
      The driver is based on v4l2-mem2mem framework.
      Signed-off-by: NSylwester Nawrocki <s.nawrocki@samsung.com>
      Signed-off-by: NKyungmin Park <kyungmin.park@samsung.com>
      Signed-off-by: NPawel Osciak <p.osciak@samsung.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      5fd8f738
  4. 03 8月, 2010 8 次提交
  5. 28 7月, 2010 1 次提交
  6. 19 5月, 2010 7 次提交
  7. 07 5月, 2010 1 次提交
  8. 27 2月, 2010 2 次提交
  9. 16 12月, 2009 2 次提交
  10. 06 12月, 2009 2 次提交
  11. 19 9月, 2009 2 次提交