Age | Commit message (Collapse) | Author |
|
The Writeback pipeline is a block in OMAP4's Display controller which can take
input from a pipeline or an overlay manager and feed it back to memory. Hence,
it allows to take benefit of the hardware processing available inside
the DISPC like color space conversion, rescaling, compositing to perform
memory-to-memory transfer with data processing or capturing a displayed frame.
The Writeback pipeline has it's own FIFO like the other pipelines. Since
Writeback isn't supported in OMAPDSS yet, we can use it's FIFO for some other
pipe which needs it. OMAP4 DISPC has a mechanism to share FIFOs among pipes
which makes this possible.
Add writeback pipeline as a member of omap_plane struct, add register offsets
for it's FIFO_SIZE_STATUS register so that the DISPC driver is aware of it's
fifo size. This would be used later to transfer the FIFO to another pipe, and
have a larger FIFO during fifomerge.
|
|
This reverts commit 7d8fd73d742489f63826f4f3166e837ad3bf1f76.
|
|
Signed-off-by: Xavier Boudet <x-boudet@ti.com>
|
|
(AG this is needed if you are not building ARCH_OMAP5)
Signed-off-by: Paolo Pisati <paolo.pisati@canonical.com>
|
|
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Signed-off-by: Vincent Stehlé <v-stehle@ti.com>
|
|
If the runtime PM of the device is disabled (for example in resume from
suspend path), it doesn't make sense to attempt pm_runtime_get/put, esp
when their return values affect the control flow path.
Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
|
|
This reverts commit 61abde21bf6272908466e2d13acd479743b4f0b3.
|
|
Signed-off-by: Jaswinder Singh <jaswinder.singh@linaro.org>
|
|
Signed-off-by: Andy Green <andy.green@linaro.org>
|
|
Signed-off-by: Andy Green <andy.green@linaro.org>
|
|
Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
|
|
Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
|
|
Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
|
|
|
|
Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
|
|
Currently the drm polls HPD every 10secs. If an unplug-plug cyles completes
within that time, we might miss the re-attach of potentially a different
display. Also if the display is plugged in immediately after the poll,
10s are quite long for power management of the link,unaware of any change
in connection, to possibly change during edid read, hence giving the
"operation stopped when reading edid" like errors.
Remedy the situation by making omapdrm provide a way for connector drivers
to call drm_helper_hpd_irq_event().
Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
|
|
Explicitly maintaining HDMI phy power state using a flag is prone to
race and un-necessary when we have a zero-cost alternative of checking
the state before trying to set it.
Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
|
|
Error is either wrong timings code or bad pixel clock.
Otherwise, we risk accepting some invalid timings but with valid pixel_clock.
Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
|
|
If the timings sent to check does not match any of the standard modes,
assume that is a custom timing and set it to VESA mode with 0 as code,
As CEA standard would need to send CEA code during the AVI info frame
and behaviour is a wrong code is sent is not understood currently on
VESA (non- Audio) non-standard timing is supported if the max pixel
clock requested is less than the maximum pixel clock supported by OMAP
for HDMI.
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
For 2d scanout at higher resolutions we need to increase the gfx
pipe dma buffer.. since we aren't using writeback pipe, assign
it's buffers to gfx.
|
|
As per design, the HDMI wrapper needs to be set to no idle when
playing audio. This is needed as the audio part in the HDMI wrapper
uses the interface clock to work. Hence, if not set to no-idle
the interface clock may be cut even when the rest of the HDMI module
is still on (as it works with the functional clock).
This is a HACK as it should be done automatically by the pm framework.
A more elegant solution is shall be implemented.
Signed-off-by: Ricardo Neri <ricardo.neri@ti.com>
|
|
The most significant nibble of the CTS value should be written in the _CTS3
register. As the CTS value was not passed correctly to the HDMI IP,
audio was played too fast.
Signed-off-by: Ricardo Neri <ricardo.neri@ti.com>
|
|
As pio driver is currently a subsidiary of DSS and thus if
PIO is made a module it will result in compiler error if DSS
is built as a module so make it is a library and call the init
function from HDMI driver as currently HDMI is the only driver which
is using it.
Reported by : Ricardo Neri <ricardo.neri@ti.com>
|
|
Temporary Patch:
Add support for TCA6424A IO expander chip in DSS to configure HDMI 3V and
5V IO to enable TPD chip.
TCA6424A also supports camera and modem and there are two instances
of it in OMAP5 so the driver should adapt to GPIO framework and should
support mutliple instances.
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
Fixed Sparse warning for
drivers/video/omap2/dss/ti_hdmi_5xxx_ip.c:594:6: warning: symbol 'hdmi_enable_video_path' was not declared.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
|
|
Resolved Sparse warning
drivers/video/omap2/dss/ti_hdmi_5xxx_ip.c:299:6: warning: symbol 'hdmi_core_infoframe_vsi_config' was not declared.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
|
|
Signed-off-by: Sebastien Guiriec <s-guiriec@ti.com>
Conflicts:
drivers/video/omap2/dss/ti_hdmi_5xxx_ip.c
|
|
Signed-off-by: Fairuz WAN ISMAIL <a0919885@ti.com>
|
|
Update OMAP5 HDMI IP definition for audio.
Signed-off-by: Sebastien Guiriec <s-guiriec@ti.com>
Conflicts:
drivers/video/omap2/dss/ti_hdmi_5xxx_ip.h
|
|
Add a config option for HDMI audio on OMAP5. Parties interested
in the functionality may select this option.
Signed-off-by: Ricardo Neri <ricardo.neri@ti.com>
|
|
Define HDMI audio operations for OMAP5 HDMI IP.
Signed-off-by: Ricardo Neri <ricardo.neri@ti.com>
|
|
Add functions to support HDMI audio configuration in OMAP5.
These functions include functions to configure the HDMI wrapper,
format and DMA settings. It also includes functions to configure
the HDMI IP core, including Audio InfoFrames, ACR packets, audio
sampler and audio parallel interface.
Signed-off-by: Ricardo Neri <ricardo.neri@ti.com>
|
|
As OMAP4 and OMAP5 have the same implementation for the audio FIFO,
it is possible to reuse the DMA configuration function for OMAP5.
However, the the format configuration function may not be reused
as some paramters are not valid for the OMAP5 HDMI IP.
Also, while there, define CTS/N calculation function for OMAP4
and OMAP5.
Signed-off-by: Ricardo Neri <ricardo.neri@ti.com>
|
|
Complete definitions for registers for the audio sampler and the audio
parallel interface in the OMAP5 HDMI IP.
Signed-off-by: Ricardo Neri <ricardo.neri@ti.com>
|
|
Add sysfs support to enable the display in 3D mode.
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
Add support to HDMI panel to configure it in 3D mode.
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
HDMI 1.4 supports HDMI to be configured in 3D mode, Add support to
configure the driver to enable in 3D mode timings in case of
full HD 3D, or to send VSI infoframe in other formats.
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
Add support for VSI configuration to send Vendor specific
data after every frame in case HDMI is enabled in 3D mode.
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
Add support for 3D formats enum's that are supported as a part of HDMI 1.4
specification.
Based-on patch by Alberto aguirre<a-aguirre@ti.com>
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
Add sysfs support for the uset space to configure limited range or full range
quantization for HDMI.
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
Support to set the quantization range to limited/full range based on the
timings that is selected, Thanks to Fairuz WAN ISMAIL <a0919885@ti.com>
for the quantization table when supported with deep color
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
Create functions which configure registers related to video packetizer,
color space converter and video sampler to add deep color support.
Signed-off-by: Archit Taneja <archit@ti.com>
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
Add support for sysfs to enable/disable deep color mode for HDMI.
Allow user to choose 24/30/36 bit output to be sent from HDMI.
Signed-off-by: Archit Taneja <archit@ti.com>
|
|
Handle the interrupt recieved from core, dummy for now.
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
Support for IRQ handling of the wrapper interrupt that
reaches HDMI is added.
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
Function to add support to enable wrapper irq is added.
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
wrapper irq init to set all the irq's to 0 is added.
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
Core block in OMAP5 HDMI is different from OMAP4. so add support
to read EDID.
Signed-off-by: Mythri P K <mythripk@ti.com>
|
|
Add the funtion pointer for OMAP5 HDMI IP.
Wrapper/PLL and PHY blocks are shared between 4 and 5.
Core block functions are made to point to OMAP5 function.
Signed-off-by: Mythri P K <mythripk@ti.com>
|