On Thu, Nov 17, 2016 at 3:45 AM, Laurent Pinchart
wrote:
> Hi Jyri,
>
> On Wednesday 16 Nov 2016 16:39:28 Jyri Sarha wrote:
>> On 11/16/16 15:33, Rob Herring wrote:
>> >> +Optional properties
>> >>
>> >>> + - reg: I2C address. If and only if present the driver node
>
> I assume you meant device no
Hi Jyri,
On Wednesday 16 Nov 2016 16:39:28 Jyri Sarha wrote:
> On 11/16/16 15:33, Rob Herring wrote:
> >> +Optional properties
> >>
> >>> + - reg: I2C address. If and only if present the driver node
I assume you meant device node, not driver node ?
> >>> + should be placed into the i2c contro
On 16/11/16 16:39, Jyri Sarha wrote:
> On 11/16/16 15:33, Rob Herring wrote:
>>> +Optional properties
+ - reg: I2C address. If and only if present the driver node
+should be placed into the i2c controller node where the
+tfp410 i2c is connected to (the current implementati
On 11/16/16 15:33, Rob Herring wrote:
>> +Optional properties
>> > + - reg: I2C address. If and only if present the driver node
>> > +should be placed into the i2c controller node where the
>> > +tfp410 i2c is connected to (the current implementation does
>> > +not yet support this).
>
On Mon, Nov 14, 2016 at 06:54:17PM +0200, Jyri Sarha wrote:
> Add very basic ti-ftp410 DVI transmitter driver. The only feature
> separating this from a completely dummy bridge is the EDID read
> support trough DDC I2C. Even that functionality should be in a
> separate generic connector driver. How
Add very basic ti-ftp410 DVI transmitter driver. The only feature
separating this from a completely dummy bridge is the EDID read
support trough DDC I2C. Even that functionality should be in a
separate generic connector driver. However, because of missing DRM
infrastructure support the connector is
