On 2012-11-21 19:57, Tony Lindgren wrote:
> * Felipe Balbi [121119 04:25]:
>> On Mon, Nov 19, 2012 at 01:09:42PM +0200, Tomi Valkeinen wrote:
>>> On 2012-11-19 11:27, Felipe Balbi wrote:
fair enough... it looks like this is going nowhere, so best we come back
to this later. No reaso
* Felipe Balbi [121119 04:25]:
> On Mon, Nov 19, 2012 at 01:09:42PM +0200, Tomi Valkeinen wrote:
> > On 2012-11-19 11:27, Felipe Balbi wrote:
> > >
> > > fair enough... it looks like this is going nowhere, so best we come back
> > > to this later. No reason to block your patch.
> >
> > Well, the
Hi,
On Mon, Nov 19, 2012 at 01:09:42PM +0200, Tomi Valkeinen wrote:
> 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 parti
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
hi,
On Mon, Nov 19, 2012 at 08:38:21AM +0200, Tomi Valkeinen wrote:
> (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 norm
(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
Hi,
On Sat, Nov 17, 2012 at 07:41:36AM +0200, Tomi Valkeinen wrote:
> 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 dri
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 OMAPDS
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 a quick look at
> >>> the drive
