Hi Tomi,
On 06/14/2013 04:52 PM, Tomi Valkeinen wrote:
Hi Tony, Roger,
I recently raised the i2c issue with reading EDID from a DVI monitor on
Panda, when booting with DT. I just couldn't get reading EDID work at
all reliably.
I now see problems with non-DT also. Booting with 3.10-rc5,
* Roger Quadros rog...@ti.com [130617 01:18]:
Hi Tomi,
On 06/14/2013 04:52 PM, Tomi Valkeinen wrote:
Hi Tony, Roger,
I recently raised the i2c issue with reading EDID from a DVI monitor on
Panda, when booting with DT. I just couldn't get reading EDID work at
all reliably.
I now
On 17/06/13 14:18, Tony Lindgren wrote:
You should be able to get the regulator based on the name just fine
from the drivers even if one driver is using DT and one is not. That is
as long as the regulator is defined. Then the regulator fwk will track
the usecount properly.
Doesn't the
* Tomi Valkeinen tomi.valkei...@ti.com [130617 04:34]:
On 17/06/13 14:18, Tony Lindgren wrote:
You should be able to get the regulator based on the name just fine
from the drivers even if one driver is using DT and one is not. That is
as long as the regulator is defined. Then the
On 06/17/2013 02:27 PM, Tomi Valkeinen wrote:
On 17/06/13 14:18, Tony Lindgren wrote:
You should be able to get the regulator based on the name just fine
from the drivers even if one driver is using DT and one is not. That is
as long as the regulator is defined. Then the regulator fwk will
Hi Tony, Roger,
I recently raised the i2c issue with reading EDID from a DVI monitor on
Panda, when booting with DT. I just couldn't get reading EDID work at
all reliably.
I now see problems with non-DT also. Booting with 3.10-rc5, with DSS
compiled into the kernel, reading EDID fails during the
