Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Dec 20, 2011

  1. ov56x0: set subdev type

    These two subdev's are sensors.
    authored December 16, 2011
  2. omap4iss: dmabuf support

    authored December 08, 2011
  3. dmabuf fixes.. squash back

    Add 'size' parameter when exporting so dmabuf->size doesn't go
    unitialized.
    authored December 08, 2011
  4. v4l2 dmabuf fixes.. squash back

    authored December 08, 2011
  5. v4l:vb2: Add dma-contig allocator as dma_buf user

    This patch makes changes for adding dma-contig as a dma_buf user. It provides
    function implementations for the {import, acquire, release, put}_dmabuf()
    mem_ops of DMABUF memory type.
    
    Signed-off-by: Sumit Semwal <sumit.semwal@ti.com>
    authored October 24, 2011 Rob Clark committed December 20, 2011
  6. v4l:vb: remove warnings about MEMORY_DMABUF

    Adding DMABUF memory type causes videobuf to complain about not using it
    in some switch cases. This patch removes these warnings.
    
    Signed-off-by: Sumit Semwal <sumit.semwal@ti.com>
    authored October 24, 2011 Rob Clark committed December 20, 2011
  7. v4l:vb2: add support for shared buffer (dma_buf)

    This patch adds support for DMABUF memory type in videobuf2. It calls relevant
    APIs of dma_buf for v4l reqbuf / qbuf / dqbuf operations.
    
    Signed-off-by: Sumit Semwal <sumit.semwal@ti.com>
    
    Conflicts:
    
    	drivers/media/video/videobuf2-core.c
    authored October 24, 2011 Rob Clark committed December 20, 2011
  8. v4l: Add DMABUF as a memory type

    Adds DMABUF memory type to v4l framework. Also adds the related file
    descriptor in v4l2_plane and v4l2_buffer.
    
    Signed-off-by: Sumit Semwal <sumit.semwal@ti.com>
    authored October 24, 2011 Rob Clark committed December 20, 2011
  9. arm: Add support for CMA for omap4iss driver

    Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
    authored November 24, 2011 Rob Clark committed December 20, 2011
  10. arm: omap4panda: Add support for omap4iss camera

    This adds support for camera interface with the support for
    following sensors:
    
    - OV5640
    - OV5650
    
    Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
    authored November 24, 2011 Rob Clark committed December 20, 2011
  11. arm: omap4430sdp: Add support for omap4iss camera

    This adds support for camera interface with the support for
    following sensors:
    
    - OV5640
    - OV5650
    
    Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
    authored November 24, 2011 Rob Clark committed December 20, 2011
  12. v4l: Add support for ov5650 sensor

    Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
    authored November 24, 2011 Rob Clark committed December 20, 2011
  13. v4l: Add support for ov5640 sensor

    This adds a very limited driver for ov5640, which
    only supports:
     - 2592x1944 @ ~7.5 fps
     - 1920x1080 @ ~15 fps,
     - 1280x720 @ ~24 fps,
     - 640x480 @ ~24 fps,
     - 320x240 @ ~24 fps,
    
    All in YUV422i format, using 1 CSI2 datalane @ 333 MHz.
    
    Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
    authored November 24, 2011 Rob Clark committed December 20, 2011
  14. v4l: Add support for omap4iss driver

    This adds a very simplistic driver to utilize the
    CSI2A interface inside the ISS subsystem in OMAP4,
    and dump the data to memory.
    
    Tested so far on omap4430sdp w/ ES2.1 GP & w/ ES2.2 EMU.
    
    Check newly added Documentation/video4linux/omap4_camera.txt
    for details.
    
    Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
    authored November 24, 2011 Rob Clark committed December 20, 2011
  15. OMAP4: Add base addresses for ISS

    NOTE: This isn't the whole list of features that the
    ISS supports, but the only ones supported at the moment.
    
    Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
    authored November 24, 2011 Rob Clark committed December 20, 2011
  16. OMAP4: hwmod: Include CSI2A and CSIPHY1 memory sections

    Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
    authored November 29, 2011 Rob Clark committed December 20, 2011
  17. v4l: Introduce sensor operation for getting interface configuration

    Introduce g_interface_parms sensor operation for getting sensor
    interface parameters. These parameters are needed from the host side
    to determine it's own configuration.
    
    Signed-off-by: Stanimir Varbanov <svarbanov@mm-sol.com>
    authored November 24, 2011 Rob Clark committed December 20, 2011
  18. mfd: twl6040: Fix wrong TWL6040_GPO3 bitfield value

    The define should be the result of 1 << Bit number.
    
    Bit number for GPOCTL.GPO3 field is 2, which results
    in 0x4 value.
    
    Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
    authored November 08, 2011 Rob Clark committed December 20, 2011
  19. TWL6030: Add mapping for auxiliary regs

    Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
    authored November 24, 2011 Rob Clark committed December 20, 2011
  20. drm/omap: dmabuf/prime support

    authored December 04, 2011

Dec 17, 2011

  1. XXX squash back into 'drm: base prime support'

    authored December 04, 2011
  2. drm: base prime support

    authored November 25, 2011 Rob Clark committed December 17, 2011

Dec 16, 2011

  1. dma-buf: Documentation for buffer sharing framework

    Add documentation for dma buffer sharing framework, explaining the
    various operations, members and API of the dma buffer sharing
    framework.
    
    Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
    Signed-off-by: Sumit Semwal <sumit.semwal@ti.com>
    authored December 01, 2011 Rob Clark committed December 16, 2011
  2. dma-buf: Introduce dma buffer sharing mechanism

    This is the first step in defining a dma buffer sharing mechanism.
    
    A new buffer object dma_buf is added, with operations and API to allow easy
    sharing of this buffer object across devices.
    
    The framework allows:
    - different devices to 'attach' themselves to this buffer, to facilitate
      backing storage negotiation, using dma_buf_attach() API.
    - association of a file pointer with each user-buffer and associated
       allocator-defined operations on that buffer. This operation is called the
       'export' operation.
    - this exported buffer-object to be shared with the other entity by asking for
       its 'file-descriptor (fd)', and sharing the fd across.
    - a received fd to get the buffer object back, where it can be accessed using
       the associated exporter-defined operations.
    - the exporter and user to share the scatterlist using map_dma_buf and
       unmap_dma_buf operations.
    
    Atleast one 'attach()' call is required to be made prior to calling the
    map_dma_buf() operation.
    
    Couple of building blocks in map_dma_buf() are added to ease introduction
    of sync'ing across exporter and users, and late allocation by the exporter.
    
    *OPTIONALLY*: mmap() file operation is provided for the associated 'fd', as
    wrapper over the optional allocator defined mmap(), to be used by devices
    that might need one.
    
    More details are there in the documentation patch.
    
    This is based on design suggestions from many people at the mini-summits[1],
    most notably from Arnd Bergmann <arnd@arndb.de>, Rob Clark <rob@ti.com> and
    Daniel Vetter <daniel@ffwll.ch>.
    
    The implementation is inspired from proof-of-concept patch-set from
    Tomasz Stanislawski <t.stanislaws@samsung.com>, who demonstrated buffer sharing
    between two v4l2 devices. [2]
    
    [1]: https://wiki.linaro.org/OfficeofCTO/MemoryManagement
    [2]: http://lwn.net/Articles/454389
    
    Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
    Signed-off-by: Sumit Semwal <sumit.semwal@ti.com>
    authored December 01, 2011 Rob Clark committed December 16, 2011
  3. drm/omap: multiplanar and YUV support

    Add support in framebuffer objects for other color formats and multi-
    planar YUV (NV12).  Since this requires changing the API between the
    plane and fb for getting scanout information (paddr, etc), take
    advantage of the opportunity and put in place a way to allow fb's to
    be unpinned when they are not being scanned out.  Now, before start
    of scanout the plane calls omap_framebuffer_pin() which takes care
    to pin all the backing bo's, then omap_framebuffer_update_scanout()
    however many times to update the scanout address(es), etc, and then
    when finished omap_framebuffer_unpin().
    
    Signed-off-by: Rob Clark <rob@ti.com>
    authored December 15, 2011
  4. drm/omap: add drm_plane support

    Because framebuffer layer and overlay scanout video pipes are basically
    thing in OMAP display subsystem (the only difference being that the first
    video pipe does not support scaling or YUV formats), much of the CRTC
    code is pulled into the plane implementation, and a private plane object
    is used by the CRTC object.  This avoids code duplication between the
    plane and CRTC.
    
    Signed-off-by: Rob Clark <rob@ti.com>
    authored December 14, 2011
  5. drm/omap: drm API update: addfb2

    Update to reflect changes in:
    "drm: add an fb creation ioctl that takes a pixel format v5"
    
    Signed-off-by: Rob Clark <rob@ti.com>
    authored December 14, 2011
  6. drm/omap: drm API update: make fops struct const

    Update to reflect changes in:
    "Make the per-driver file_operations struct const"
    
    Signed-off-by: Rob Clark <rob@ti.com>
    authored December 12, 2011
  7. drm: add support for private planes

    In cases where the scanout hw is sufficiently similar between "overlay"
    and traditional crtc layers, it might be convenient to allow the driver
    to create internal drm_plane helper objects used by the drm_crtc
    implementation, rather than duplicate code between the plane and crtc.
    A private plane is not exposed to userspace.
    
    Signed-off-by: Rob Clark <rob@ti.com>
    authored December 13, 2011
  8. drm: disconnect plane from fb/crtc when disabled

    Since plane->fb and plane->crtc are set in drm_mode_setplane()
    after update_plane(), They should be cleared after disable().
    
    Signed-off-by: Rob Clark <rob@ti.com>
    authored December 13, 2011
  9. Merge branch 'drm-next' of git://people.freedesktop.org/~airlied/linu…

    …x into drmplane
    
    Conflicts:
    	drivers/gpu/drm/nouveau/nouveau_sgdma.c
    authored December 16, 2011
  10. Andy Gross

    drm/omap: add debugfs support

    Right now just a tiler_map file to dump a 2d map of which areas in
    tiler/dmm have pinned buffers (or reservations).  In the future more
    could be added.
    
    Signed-off-by: Rob Clark <rob@ti.com>
    authored December 15, 2011 Rob Clark committed December 16, 2011
  11. drm/omap: avoid aquiring mutex in atomic context (v2)

    omap_gem_roll() could be called by fbcon in atomic context or when
    struct_mutext is held.  Avoid aquiring mutex (deadlock), or calling
    tiler_pin() (which itself is not safe for atomic context) in these
    cases.
    
    Signed-off-by: Rob Clark <rob@ti.com>
    authored December 15, 2011

Dec 15, 2011

  1. drm/omap: add ywrap module param

    Can be set at boot or module load time to prevent YWRAP scrolling from
    being enabled.
    
    Signed-off-by: Rob Clark <rob@ti.com>
    authored December 11, 2011
  2. drm: call connector dpms fxn, when setting config

    Call connector->funcs->dpms(DPMS_ON) rather than just setting
    connector->dpms = DPMS_ON.  This ensures that if the connector
    has something to do to enable the output (rather than just using
    drm_helper_connector_dpms helper directly), that this happens
    at bootup.  This solves an issue with connectors not getting
    enabled from fbcon_init() when the driver is loaded.
    
    Signed-off-by: Rob Clark <rob@ti.com>
    authored December 15, 2011
Something went wrong with that request. Please try again.