Eric Lee / smarc-ti-linux-kernel

13 Nov, 2012

1 commit

  • 0049fb260   OMAPFB: use dma_alloc_attrs to allocate memory ... Browse Code »

    Use dma_alloc_attrs to allocate memory instead of omap specific vram
    allocator. After this we can remove the omap vram allocator.

    There are some downsides to this change:

    1) dma_alloc_attrs doesn't let us allocate at certain physical address.
    However, this should not be a problem as this feature of vram allocator
    is only used when reserving the framebuffer that was initialized by the
    bootloader, and we don't currently support "passing" a framebuffer from
    the bootloader to the kernel anyway.

    2) dma_alloc_attrs, as of now, always ioremaps the allocated area, and
    we don't need the ioremap when using VRFB. This patch uses
    DMA_ATTR_NO_KERNEL_MAPPING for the allocation, but the flag is currently
    not operational.

    3) OMAPFB_GET_VRAM_INFO ioctl cannot return real values anymore. I
    changed the ioctl to return 64M for all the values, which, I hope, the
    applications will interpret as "there's enough vram".

    4) "vram" kernel parameter to define how much ram to reserve for video
    use no longer works. The user needs to enable CMA and use "cma"
    parameter.

    Signed-off-by: Tomi Valkeinen

    Tomi Valkeinen
     

11 May, 2012

2 commits

  • 9c0b84203   OMAPDSS: Provide an interface for audio support ... Browse Code »

    There exist several display technologies and standards that support audio as
    well. Hence, it is relevant to update the DSS device driver to provide an audio
    interface that may be used by an audio driver or any other driver interested in
    the functionality.

    The audio_enable function is intended to prepare the relevant
    IP for playback (e.g., enabling an audio FIFO, taking in/out of reset
    some IP, enabling companion chips, etc). It is intended to be called before
    audio_start. The audio_disable function performs the reverse operation and is
    intended to be called after audio_stop.

    While a given DSS device driver may support audio, it is possible that for
    certain configurations audio is not supported (e.g., an HDMI display using a
    VESA video timing). The audio_supported function is intended to query whether
    the current configuration of the display supports audio.

    The audio_config function is intended to configure all the relevant audio
    parameters of the display. In order to make the function independent of any
    specific DSS device driver, a struct omap_dss_audio is defined. Its purpose
    is to contain all the required parameters for audio configuration. At the
    moment, such structure contains pointers to IEC-60958 channel status word and
    CEA-861 audio infoframe structures. This should be enough to support HDMI and
    DisplayPort, as both are based on CEA-861 and IEC-60958. The omap_dss_audio
    structure may be extended in the future if required.

    The audio_enable/disable, audio_config and audio_supported functions could be
    implemented as functions that may sleep. Hence, they should not be called
    while holding a spinlock or a readlock.

    The audio_start/audio_stop function is intended to effectively start/stop audio
    playback after the configuration has taken place. These functions are designed
    to be used in an atomic context. Hence, audio_start should return quickly and be
    called only after all the needed resources for audio playback (audio FIFOs,
    DMA channels, companion chips, etc) have been enabled to begin data transfers.
    audio_stop is designed to only stop the audio transfers. The resources used
    for playback are released using audio_disable.

    A new enum omap_dss_audio_state is introduced to help the implementations of
    the interface to keep track of the audio state. The initial state is _DISABLED;
    then, the state transitions to _CONFIGURED, and then, when it is ready to
    play audio, to _ENABLED. The state _PLAYING is used when the audio is being
    rendered.

    Signed-off-by: Ricardo Neri

    Ricardo Neri
     
  • 0aca3c63e   OMAPDSS: VENC: allow switching venc output type at runtime ... Browse Code »

    VENC output type (composite/svideo) doesn't have to be fixed by board
    wiring, it is possible to also provide composite signal through svideo
    luminance connector (software enabled), which is what pandora does.

    Having to recompile the kernel for users who have TV connector types
    that don't match default board setting is very inconvenient, especially
    for users of a consumer device, so add support for switching VENC output
    type at runtime over a new sysfs file output_type.

    Signed-off-by: Grazvydas Ignotas
    Signed-off-by: Tomi Valkeinen

    Grazvydas Ignotas
     

10 Nov, 2010

1 commit

09 Dec, 2009

1 commit