On Wed, 18 Apr 2018 10:02:12 +0200
Peter Rosin wrote:
> On 2018-04-18 09:36, Boris Brezillon wrote:
> > On Tue, 17 Apr 2018 15:10:51 +0200
> > Peter Rosin wrote:
> >
> >> When the of-graph points to a tda998x-compatible HDMI encoder, register
> >> as a
On Wed, 18 Apr 2018 10:02:12 +0200
Peter Rosin wrote:
> On 2018-04-18 09:36, Boris Brezillon wrote:
> > On Tue, 17 Apr 2018 15:10:51 +0200
> > Peter Rosin wrote:
> >
> >> When the of-graph points to a tda998x-compatible HDMI encoder, register
> >> as a component master and bind to the
On 2018-04-18 09:36, Boris Brezillon wrote:
> On Tue, 17 Apr 2018 15:10:51 +0200
> Peter Rosin wrote:
>
>> When the of-graph points to a tda998x-compatible HDMI encoder, register
>> as a component master and bind to the encoder/connector provided by
>> the tda998x driver.
>
>
On 2018-04-18 09:36, Boris Brezillon wrote:
> On Tue, 17 Apr 2018 15:10:51 +0200
> Peter Rosin wrote:
>
>> When the of-graph points to a tda998x-compatible HDMI encoder, register
>> as a component master and bind to the encoder/connector provided by
>> the tda998x driver.
>
> Can't we do the
On Tue, 17 Apr 2018 15:10:51 +0200
Peter Rosin wrote:
> When the of-graph points to a tda998x-compatible HDMI encoder, register
> as a component master and bind to the encoder/connector provided by
> the tda998x driver.
Can't we do the opposite: make the tda998x driver expose
On Tue, 17 Apr 2018 15:10:51 +0200
Peter Rosin wrote:
> When the of-graph points to a tda998x-compatible HDMI encoder, register
> as a component master and bind to the encoder/connector provided by
> the tda998x driver.
Can't we do the opposite: make the tda998x driver expose its devices as
drm
6 matches
Mail list logo