Hi Andrzej,
On Monday, 18 December 2017 10:43:51 EET Andrzej Hajda wrote:
> On 15.12.2017 16:54, Daniel Vetter wrote:
> > On Fri, Dec 15, 2017 at 01:30:24PM +0100, Linus Walleij wrote:
> >> On Fri, Dec 15, 2017 at 1:10 PM, Linus Walleij
wrote:
> >>> - The connector is apparently not the right ab
Hi Daniel,
On Friday, 15 December 2017 17:54:15 EET Daniel Vetter wrote:
> On Fri, Dec 15, 2017 at 01:30:24PM +0100, Linus Walleij wrote:
> > On Fri, Dec 15, 2017 at 1:10 PM, Linus Walleij
wrote:
> >> - The connector is apparently not the right abstraction to carry
> >> the detailed timings sp
On 15.12.2017 16:54, Daniel Vetter wrote:
> On Fri, Dec 15, 2017 at 01:30:24PM +0100, Linus Walleij wrote:
>> On Fri, Dec 15, 2017 at 1:10 PM, Linus Walleij
>> wrote:
>>
>>> - The connector is apparently not the right abstraction to carry
>>> the detailed timings specification between DRI drive
On Fri, Dec 15, 2017 at 01:30:24PM +0100, Linus Walleij wrote:
> On Fri, Dec 15, 2017 at 1:10 PM, Linus Walleij
> wrote:
>
> > - The connector is apparently not the right abstraction to carry
> > the detailed timings specification between DRI drivers and bridge
> > drivers.
> >
> > - Instead
On Fri, Dec 15, 2017 at 1:10 PM, Linus Walleij wrote:
> - The connector is apparently not the right abstraction to carry
> the detailed timings specification between DRI drivers and bridge
> drivers.
>
> - Instead put detailed timing data into the bridge itself as an
> optional information
This patch set is in response to Laurent's mail:
https://www.spinics.net/lists/dri-devel/msg155618.html
So in summary:
- The connector is apparently not the right abstraction to carry
the detailed timings specification between DRI drivers and bridge
drivers.
- Instead put detailed timing data