11 Jan, 2012

1 commit

  • Add driver for the JPEG codec IP block available in Samsung Exynos SoC series.

    The driver is implemented as a V4L2 mem-to-mem device. It exposes two video
    nodes to user space, one for the encoding part, and one for the decoding part.

    Signed-off-by: Andrzej Pietrasiewicz
    Signed-off-by: Kyungmin Park
    Reviewed-by: Sakari Ailus
    Reviewed-by: Sylwester Nawrocki
    Reviewed-by: Tomasz Stanislawski
    Signed-off-by: Marek Szyprowski
    Signed-off-by: Mauro Carvalho Chehab

    Andrzej Pietrasiewicz
     

20 Dec, 2011

1 commit

  • This patch adds the driver for the as3645a LED flash controller. This
    controller supports a high power led in flash and torch modes and an
    indicator light, sometimes also called privacy light.

    Signed-off-by: Laurent Pinchart
    Signed-off-by: Andy Shevchenko
    Signed-off-by: Nayden Kanchev
    Signed-off-by: Tuukka Toivonen
    Signed-off-by: Antti Koskipaa
    Signed-off-by: Stanimir Varbanov
    Signed-off-by: Vimarsh Zutshi
    Signed-off-by: Sakari Ailus
    Signed-off-by: Ivan T. Ivanov
    Signed-off-by: Mika Westerberg
    Signed-off-by: David Cohen
    Signed-off-by: Mauro Carvalho Chehab

    Laurent Pinchart
     

08 Nov, 2011

8 commits


04 Nov, 2011

1 commit

  • This driver exposes preview mode operation of the S5K6AAFX sensor with
    embedded SoC ISP. The native capture (snapshot) operation mode is not
    supported.
    Following controls are available:
    manual/auto exposure and gain, power line frequency (anti-flicker),
    saturation, sharpness, brightness, contrast, white balance temperature,
    color effects, horizontal/vertical image flip, frame interval,
    auto white balance.
    RGB component gains are currently exposed through private controls.

    Reviewed-by: Sakari Ailus
    Signed-off-by: Sylwester Nawrocki
    Signed-off-by: Kyungmin Park
    Signed-off-by: Mauro Carvalho Chehab

    Sylwester Nawrocki
     

03 Nov, 2011

1 commit


01 Nov, 2011

1 commit

  • * 'v4l_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media: (348 commits)
    [media] pctv452e: Remove bogus code
    [media] adv7175: Make use of media bus pixel codes
    [media] media: vb2: fix incorrect return value
    [media] em28xx: implement VIDIOC_ENUM_FRAMESIZES
    [media] cx23885: Stop the risc video fifo before reconfiguring it
    [media] cx23885: Avoid incorrect error handling and reporting
    [media] cx23885: Avoid stopping the risc engine during buffer timeout
    [media] cx23885: Removed a spurious function cx23885_set_scale()
    [media] cx23885: v4l2 api compliance, set the audioset field correctly
    [media] cx23885: hook the audio selection functions into the main driver
    [media] cx23885: add generic functions for dealing with audio input selection
    [media] cx23885: fixes related to maximum number of inputs and range checking
    [media] cx23885: Initial support for the MPX-885 mini-card
    [media] cx25840: Ensure AUDIO6 and AUDIO7 trigger line-in baseband use
    [media] cx23885: Enable audio line in support from the back panel
    [media] cx23885: Allow the audio mux config to be specified on a per input basis
    [media] cx25840: Enable support for non-tuner LR1/LR2 audio inputs
    [media] cx23885: Name an internal i2c part and declare a bitfield by name
    [media] cx23885: Ensure VBI buffers timeout quickly - bugfix for vbi hangs during streaming
    [media] cx23885: remove channel dump diagnostics when a vbi buffer times out
    ...

    Fix up trivial conflicts in drivers/misc/altera-stapl/altera.c (header
    file rename vs add)

    Linus Torvalds
     

08 Oct, 2011

1 commit

  • Both mt9t001.c and mt9p031.c have two identical issues, those
    being that they will need module.h inclusion for the upcoming
    cleanup going on there, and that their dependencies don't limit
    selection of configs that will fail to compile as follows:

    The related config options are CONFIG_MEDIA_CONTROLLER and
    CONFIG_VIDEO_V4L2_SUBDEV_API. Looking at the code, it appears
    that the driver was never intended to work without these enabled,
    so add a dependency on CONFIG_VIDEO_V4L2_SUBDEV_API, which in
    turn already has a dependency on CONFIG_MEDIA_CONTROLLER.

    Reported-by: Randy Dunlap
    Signed-off-by: Paul Gortmaker
    Acked-by: Randy Dunlap
    Signed-off-by: Mauro Carvalho Chehab

    Paul Gortmaker
     

23 Sep, 2011

1 commit


22 Sep, 2011

3 commits

  • The MT9T001 is a parallel 3MP sensor from Aptina (formerly Micron)
    controlled through I2C.

    The driver creates a V4L2 subdevice. It currently supports binning and
    cropping, and the gain, exposure, test pattern and black level controls.

    Signed-off-by: Laurent Pinchart
    Signed-off-by: Mauro Carvalho Chehab

    Laurent Pinchart
     
  • SR030PC30, NOON010PC30, M5MOLS are camera sensors so better place
    for them is under the "Camera sensors" Kconfig section.

    Signed-off-by: Sylwester Nawrocki
    Signed-off-by: Kyungmin Park
    Signed-off-by: Mauro Carvalho Chehab

    Sylwester Nawrocki
     
  • Replace g/s_mbus_fmt ops with the pad level get/set_fmt operations.
    Add media entity initialization and set subdev flags so the host driver
    creates a subdev device node for the driver.
    A mutex was added for serializing the subdev operations. When setting
    format is attempted during streaming an (EBUSY) error will be returned.

    After the device is powered up it will now remain in "power sleep"
    mode until s_stream(1) is called. The "power sleep" mode is used
    to suspend/resume frame generation at the sensor's output through
    s_stream op.

    Signed-off-by: Sylwester Nawrocki
    Signed-off-by: Kyungmin Park
    Acked-by: Laurent Pinchart
    Signed-off-by: Mauro Carvalho Chehab

    Sylwester Nawrocki
     

14 Sep, 2011

1 commit

  • Without this patch it is possible to select the VIDEO_OMAP3
    driver which then selects OMAP_IOVMM. But the omap iommu
    driver is not compiled without IOMMU_SUPPORT enabled. Fix
    that by forcing OMAP_IOMMU and OMAP_IOVMM are enabled before
    VIDEO_OMAP3 can be selected.

    Cc: Ohad Ben-Cohen
    Cc: iommu@lists.linux-foundation.org
    Cc: linux-kernel@vger.kernel.org
    Signed-off-by: Joerg Roedel

    Joerg Roedel
     

11 Sep, 2011

1 commit

  • The MT9P031 is a parallel 12-bit 5MP sensor from Aptina (formerly
    Micron) controlled through I2C.

    The driver creates a V4L2 subdevice. It currently supports skipping,
    cropping, automatic binning, and gain, exposure, h/v flip and test
    pattern controls.

    Signed-off-by: Javier Martin
    Signed-off-by: Laurent Pinchart
    Signed-off-by: Mauro Carvalho Chehab

    Javier Martin
     

07 Sep, 2011

2 commits

  • Add a top level media device driver aggregating FIMC video devnodes,
    MIPI-CSIS and sensor subdevs. This driver gathers all media entities
    and creates the possible links between them during initialization. By
    default some links will be activated to enable access to all available
    sensors in the system. For example if there are sensors S0, S1 listed
    in the media device platform data definition they will be by default
    assigned to FIMC0, FIMC1 respectively, which in turn will corresponds
    to separate /dev/video?.
    There is enough FIMC H/W entities to cover all available physical camera
    interfaces in the system.

    The fimc media device driver is bound to the "s5p-fimc-md" platform device.
    Such platform device should be created by board initialization code
    and camera sensors description array need to be specified as its
    platform data.

    The media device driver also implements various video pipeline operations,
    for enabling subdevs power, streaming, etc., which will be used by the
    capture video node driver.

    Signed-off-by: Sylwester Nawrocki
    Signed-off-by: Kyungmin Park
    Signed-off-by: Mauro Carvalho Chehab

    Sylwester Nawrocki
     
  • Add runtime PM and system sleep support in the memory-to-memory
    driver. It's required to enable the FIMC operation on Exynos4
    SoCs. This patch prevents system boot failure when the driver
    is compiled in, as it now tries to access its I/O memory without
    first enabling the corresponding power domain.

    The camera capture device suspend/resume is not fully covered,
    the capture device is just powered on/off during the video
    node open/close. However this enables it's normal operation
    on Exynos4 SoCs.

    [mchehab@redhat.com: fix a small checkpatch error]
    Signed-off-by: Sylwester Nawrocki
    Signed-off-by: Kyungmin Park
    Signed-off-by: Mauro Carvalho Chehab

    Sylwester Nawrocki
     

26 Aug, 2011

1 commit

  • Move OMAP's iommu drivers to the dedicated iommu drivers folder.

    While OMAP's iovmm (virtual memory manager) driver does not strictly
    belong to the iommu drivers folder, move it there as well, because
    it's by no means OMAP-specific (in concept. technically it is still
    coupled with OMAP's iommu).

    Eventually, iovmm will be completely replaced with the generic,
    iommu-based, dma-mapping API.

    Signed-off-by: Ohad Ben-Cohen
    Acked-by: Laurent Pinchart
    Acked-by: Hiroshi DOYU
    Acked-by: Tony Lindgren
    Signed-off-by: Joerg Roedel

    Ohad Ben-Cohen
     

28 Jul, 2011

6 commits


26 May, 2011

1 commit


25 May, 2011

2 commits


21 May, 2011

1 commit

  • The helper chips are classified by their function. Unfortunaltely,
    with time, developers added their stuff into the wrong places.

    Fix it by moving itens to be at the right place. Also add a new
    category for sensors and for misc devices that are found only on
    a certain specific board.

    While here, fix two bad whitespaces at Kconfig.

    Signed-off-by: Mauro Carvalho Chehab

    Mauro Carvalho Chehab
     

20 May, 2011

4 commits


13 Apr, 2011

1 commit

  • Since commit

    379fa5d ([media] V4L: mx3_camera: convert to videobuf2)

    mx3_camera uses videobuf2, but that commit didn't upgrade the select
    resulting in the following build failure:

    drivers/built-in.o: In function `mx3_camera_init_videobuf':
    clkdev.c:(.text+0x86580): undefined reference to `vb2_dma_contig_memops'
    drivers/built-in.o: In function `mx3_camera_probe':
    clkdev.c:(.devinit.text+0x3548): undefined reference to `vb2_dma_contig_init_ctx'
    clkdev.c:(.devinit.text+0x3578): undefined reference to `vb2_dma_contig_cleanup_ctx'
    drivers/built-in.o: In function `mx3_camera_remove':
    clkdev.c:(.devexit.text+0x674): undefined reference to `vb2_dma_contig_cleanup_ctx'
    make[2]: *** [.tmp_vmlinux1] Error 1
    make[1]: *** [sub-make] Error 2
    make: *** [all] Error 2

    Signed-off-by: Uwe Kleine-König
    Signed-off-by: Guennadi Liakhovetski
    Signed-off-by: Mauro Carvalho Chehab

    Uwe Kleine-König
     

22 Mar, 2011

2 commits

  • Add the OMAP3 ISP driver to the kernel build system.

    Signed-off-by: Laurent Pinchart
    Acked-by: Hans Verkuil
    Signed-off-by: Mauro Carvalho Chehab

    Laurent Pinchart
     
  • This soc_camera driver is for Omnivision's OV9740 sensor. This initial
    submission provides support for YUV422 output at 1280x720 (720p), which is
    the sensor's native resolution. 640x480 (VGA) is also supported, with
    cropping and scaling performed by the sensor's ISP.

    This driver is heavily based off of the existing OV9640 driver.

    Signed-off-by: Andrew Chew
    Signed-off-by: Guennadi Liakhovetski
    Signed-off-by: Mauro Carvalho Chehab

    Andrew Chew