On 9/15/2015 9:13 PM, Rob Herring wrote:
On 09/15/2015 05:32 AM, Archit Taneja wrote:
Hi Rob, Mark,
We've been trying to figure out the right way to represent a class
of display encoder devices in DT.
I've been meaning to reply on this.
These devices have registers that are generally conf
On 09/15/2015 05:32 AM, Archit Taneja wrote:
> Hi Rob, Mark,
>
> We've been trying to figure out the right way to represent a class
> of display encoder devices in DT.
I've been meaning to reply on this.
> These devices have registers that are generally configured via i2c. Once
> the device is c
Hi Rob, Mark,
We've been trying to figure out the right way to represent a class
of display encoder devices in DT.
These devices have registers that are generally configured via i2c. Once
the device is configured, it takes in video data from the mipi
dsi bus.
Until now, all the devices we've
Hi Rob, Mark,
We've been trying to figure out the right way to represent a class
of display encoder devices in DT.
These devices have registers that are generally configured via i2c. Once
the device is configured, it takes in video data from the mipi
dsi bus.
Until now, all the devices we've
On Thu, Sep 10, 2015 at 11:45:35AM +0530, Archit Taneja wrote:
>
>
> On 09/08/2015 03:57 PM, Andrzej Hajda wrote:
> >On 09/07/2015 01:46 PM, Archit Taneja wrote:
> >>Thierry,
> >>
> >>On 08/21/2015 11:39 AM, Archit Taneja wrote:
> >>>
> >>>
> >>>On 08/20/2015 05:18 PM, Thierry Reding wrote:
> >>>
On 09/08/2015 03:57 PM, Andrzej Hajda wrote:
On 09/07/2015 01:46 PM, Archit Taneja wrote:
Thierry,
On 08/21/2015 11:39 AM, Archit Taneja wrote:
On 08/20/2015 05:18 PM, Thierry Reding wrote:
On Thu, Aug 20, 2015 at 09:46:14AM +0530, Archit Taneja wrote:
Hi Thierry, Lucas,
On 08/19/2015
On 09/07/2015 01:46 PM, Archit Taneja wrote:
> Thierry,
>
> On 08/21/2015 11:39 AM, Archit Taneja wrote:
>>
>>
>> On 08/20/2015 05:18 PM, Thierry Reding wrote:
>>> On Thu, Aug 20, 2015 at 09:46:14AM +0530, Archit Taneja wrote:
Hi Thierry, Lucas,
On 08/19/2015 08:32 PM, Thierry
Thierry,
On 08/21/2015 11:39 AM, Archit Taneja wrote:
On 08/20/2015 05:18 PM, Thierry Reding wrote:
On Thu, Aug 20, 2015 at 09:46:14AM +0530, Archit Taneja wrote:
Hi Thierry, Lucas,
On 08/19/2015 08:32 PM, Thierry Reding wrote:
On Wed, Aug 19, 2015 at 04:52:24PM +0200, Lucas Stach wrote:
On 08/20/2015 05:18 PM, Thierry Reding wrote:
On Thu, Aug 20, 2015 at 09:46:14AM +0530, Archit Taneja wrote:
Hi Thierry, Lucas,
On 08/19/2015 08:32 PM, Thierry Reding wrote:
On Wed, Aug 19, 2015 at 04:52:24PM +0200, Lucas Stach wrote:
Am Mittwoch, den 19.08.2015, 16:34 +0200 schrieb Thierr
On Thu, Aug 20, 2015 at 09:46:14AM +0530, Archit Taneja wrote:
> Hi Thierry, Lucas,
>
>
> On 08/19/2015 08:32 PM, Thierry Reding wrote:
> >On Wed, Aug 19, 2015 at 04:52:24PM +0200, Lucas Stach wrote:
> >>Am Mittwoch, den 19.08.2015, 16:34 +0200 schrieb Thierry Reding:
> >>>On Wed, Aug 19, 2015 at
Hi Thierry, Lucas,
On 08/19/2015 08:32 PM, Thierry Reding wrote:
On Wed, Aug 19, 2015 at 04:52:24PM +0200, Lucas Stach wrote:
Am Mittwoch, den 19.08.2015, 16:34 +0200 schrieb Thierry Reding:
On Wed, Aug 19, 2015 at 04:17:08PM +0200, Lucas Stach wrote:
Hi Thierry, Archit,
[...]
Perhaps a b
On Wed, 19 Aug 2015, Thierry Reding wrote:
> On Wed, Aug 19, 2015 at 04:52:24PM +0200, Lucas Stach wrote:
>> Am Mittwoch, den 19.08.2015, 16:34 +0200 schrieb Thierry Reding:
>> > I think that's a flawed interpretation of what's going on here. The
>> > device in fact has two interfaces: one is I2C,
On Wed, Aug 19, 2015 at 04:52:24PM +0200, Lucas Stach wrote:
> Am Mittwoch, den 19.08.2015, 16:34 +0200 schrieb Thierry Reding:
> > On Wed, Aug 19, 2015 at 04:17:08PM +0200, Lucas Stach wrote:
> > > Hi Thierry, Archit,
> > >
> [...]
> > > > Perhaps a better way would be to invert this relationship
Am Mittwoch, den 19.08.2015, 16:34 +0200 schrieb Thierry Reding:
> On Wed, Aug 19, 2015 at 04:17:08PM +0200, Lucas Stach wrote:
> > Hi Thierry, Archit,
> >
[...]
> > > Perhaps a better way would be to invert this relationship. According to
> > > your proposal we'd have to have DT like this:
> > >
On Wed, Aug 19, 2015 at 04:17:08PM +0200, Lucas Stach wrote:
> Hi Thierry, Archit,
>
> Am Mittwoch, den 19.08.2015, 15:13 +0200 schrieb Thierry Reding:
> > On Wed, Aug 19, 2015 at 10:37:54AM +0530, Archit Taneja wrote:
> > > Hi,
> > >
> > > On 06/30/2015 10:54 AM, Archit Taneja wrote:
> > > >We a
Hi Thierry, Archit,
Am Mittwoch, den 19.08.2015, 15:13 +0200 schrieb Thierry Reding:
> On Wed, Aug 19, 2015 at 10:37:54AM +0530, Archit Taneja wrote:
> > Hi,
> >
> > On 06/30/2015 10:54 AM, Archit Taneja wrote:
> > >We are currently restricted when it comes to supporting DSI on devices
> > >that
On Wed, Aug 19, 2015 at 10:37:54AM +0530, Archit Taneja wrote:
> Hi,
>
> On 06/30/2015 10:54 AM, Archit Taneja wrote:
> >We are currently restricted when it comes to supporting DSI on devices
> >that have a non-DSI control bus. For example, DSI encoder chips are
> >available in the market that are
Hi,
On 06/30/2015 10:54 AM, Archit Taneja wrote:
We are currently restricted when it comes to supporting DSI on devices
that have a non-DSI control bus. For example, DSI encoder chips are
available in the market that are configured via i2c. Configuring their
registers via DSI bus is either optio
We are currently restricted when it comes to supporting DSI on devices
that have a non-DSI control bus. For example, DSI encoder chips are
available in the market that are configured via i2c. Configuring their
registers via DSI bus is either optional or not available at all.
These devices still ne
19 matches
Mail list logo
