On 12/01/15 10:43, Joonyoung Shim wrote:
+Cc Tomi Valkeinen,
Hi Uwe,
On 01/12/2015 04:50 PM, Uwe Kleine-König wrote:
Hello,
On Mon, Jan 12, 2015 at 11:53:02AM +0900, Joonyoung Shim wrote:
This is required in order to ensure that core system devices such as
voltage regulators attached
On 2012-11-19 11:27, Felipe Balbi wrote:
If we had a separate, independent i2c-edid driver, we'd have to somehow
link the i2c-edid driver and tfp410 (or whatever driver would handle the
video link in that particular case) so that the i2c-edid driver would
know about hotplug events. We would
(dropping Tony and stable)
On 2012-11-18 13:34, Felipe Balbi wrote:
how are you toggling the gpio ? You said tfp410 isn't controlled at all
except for the power down gpio. Who provides the gpio ?
It's a normal OMAP GPIO, going to TFP410. I use gpio_set_value() to
set/unset it.
Well, it's
On 2012-11-16 15:51, Felipe Balbi wrote:
Hi,
On Fri, Nov 16, 2012 at 02:22:33PM +0200, Tomi Valkeinen wrote:
The i2c handling in tfp410 driver, which handles converting parallel RGB
to DVI, was changed in 958f2717b84e88bf833d996997fda8f73276f2af. The
commit summary should be added
On 2012-11-16 17:19, Felipe Balbi wrote:
Hi,
On Fri, Nov 16, 2012 at 04:27:01PM +0200, Tomi Valkeinen wrote:
On 2012-11-16 15:51, Felipe Balbi wrote:
Hi,
On Fri, Nov 16, 2012 at 02:22:33PM +0200, Tomi Valkeinen wrote:
The i2c handling in tfp410 driver, which handles converting parallel
On 2012-11-16 20:21, Felipe Balbi wrote:
Hi,
On Fri, Nov 16, 2012 at 05:39:44PM +0200, Tomi Valkeinen wrote:
To be fair, the whole i2c_bus_num looks like a big hackery introduced by
the way panel drivers are written for OMAP DSS.
TFP410 is an I2C client, not an OMAPDSS client. After
