Re: [PATCH] ARM: vexpress: initial device tree support

[Timur Tabi <timur-KZfg59tc24xl57MIdRCFDg@public.gmane.org>]

Stephen Warren wrote:
> For monitors attached to user-accessible connectors, whenever the 
> user physically plugs in a new monitor, you need to read the EDID 
> since it could be a new monitor. DVI and HDMI have explicit hotplug 
> detect lines to trigger this. I'm not sure how it works for VGA; 
> perhaps you have to manually reprobe.

We're using DVI, but it turns out that the interrupt signal on the video encoder (TFP410) is not connected to anything on our board, so I can't receive any interrupts.  The only way I would be able to tell is to create a kernel timer to poll the TFP410 through I2C, which I really don't want to do.

> Of course, if this thread is talking about built-in LCD displays 
> where the connectivity is fixed, this is a non-issue, but it's still 
> a relevant general design discussion; hopefully whatever solution 
> that's picked would work for DVI/HDMI even if you're dealing with 
> LCDs right now.

My board supports both LVDS and DVI, and the LVDS is connected to a built-in display, so I need to support both hotplug and non-hotplug.

I also noticed that the I2C interface is not enabled until after the console opens the framebuffer.  That means it's impossible for EDID data to be available before the console switches to the video device.  That doesn't seem right.

-- 
Timur Tabi
Linux kernel developer at Freescale