Thread (36 messages) flat view 36 messages, 4 authors, 2011-09-19

Re: [PATCHv2 09/15] OMAP: DSS2: HDMI: implement detect()

From: Tomi Valkeinen <hidden>
Date: 2011-09-12 16:18:01
Also in: linux-omap

On Mon, 2011-09-12 at 18:54 +0530, K, Mythri P wrote:
Hi Tomi,

On Mon, Sep 12, 2011 at 2:43 PM, Tomi Valkeinen [off-list ref] wrote:
quoted
Implement detect() by checking the hot plug detect status.

The implementation is not very good, as it always turns on the HDMI
output to get the detection working. HDMI driver needs improvements so
that we could enable only core parts of it.

Cc: Mythri P K <redacted>
Signed-off-by: Tomi Valkeinen <redacted>
---
<snip>
quoted
+bool ti_hdmi_4xxx_detect(struct hdmi_ip_data *ip_data)
+{
+       int r;
+
+       void __iomem *base = hdmi_core_sys_base(ip_data);
+
+       /* HPD */
+       r = REG_GET(base, HDMI_CORE_SYS_SYS_STAT, 1, 1);
+
+       return r = 1;
+}
+
For HPD the probe should also be on the core interrupt first , and the
detect should be dynamic, ie based on the cable connect and disconnect
event.So this approach for HPD is not really the way.
This is not for the event, this is for polling. There is currently no
hot plug event mechanism in the DSS.

Do we get an interrupt when the driver is loaded and the cable is
already connected? And do you plan to keep the plugged in/out state
stored somewhere, or how do you implement detect()?
Also that should be based on the GPIO(63) , I am planning to push a
patch on that shortly.
What is gpio 63? What does the HDMI_CORE_SYS_STAT HDP bit tell us then?

 Tomi

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help