[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <26d4d0c2-b59a-40ad-57d1-ab2677253b71@axentia.se>
Date: Mon, 27 Aug 2018 22:48:11 +0200
From: Peter Rosin <peda@...ntia.se>
To: Boris Brezillon <boris.brezillon@...tlin.com>
Cc: linux-kernel@...r.kernel.org, David Airlie <airlied@...ux.ie>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, Jyri Sarha <jsarha@...com>,
Daniel Vetter <daniel@...ll.ch>,
Andrzej Hajda <a.hajda@...sung.com>,
Russell King - ARM Linux <linux@...linux.org.uk>,
Jacopo Mondi <jacopo+renesas@...ndi.org>,
Sakari Ailus <sakari.ailus@....fi>
Subject: Re: [PATCH v9 0/4] drm/atmel-hlcdc: bus-width override support
On 2018-08-27 22:40, Boris Brezillon wrote:
> On Mon, 27 Aug 2018 22:35:05 +0200
> Boris Brezillon <boris.brezillon@...tlin.com> wrote:
>
>> On Mon, 27 Aug 2018 22:31:22 +0200
>> Peter Rosin <peda@...ntia.se> wrote:
>>
>>> On 2018-08-27 21:24, Boris Brezillon wrote:
>>>> On Sat, 25 Aug 2018 10:56:16 +0200
>>>> Peter Rosin <peda@...ntia.se> wrote:
>>>>
>>>>> Hi!
>>>>>
>>>>> The background for these patches is that our PCB interface between
>>>>> the SAMA5D3 and the ds90c185 lvds encoder is only using 16 bits, and
>>>>> this has to be described somewhere, or the atmel-hlcdc driver have no
>>>>> chance of selecting the correct output mode. Since we have similar
>>>>> problems with a tda19988 HDMI encoder I added patches to override
>>>>> the atmel-hlcdc output format via DT properties compatible with the
>>>>> media video-interface binding and things start to play together.
>>>>
>>>> Queued to drm-misc-next.
>>>
>>> Thanks!
>>>
>>> Minute issue, you seem to have some spell-check going on or something,
>>> because the subject of patch 1/4 has been "corrected" from
>>> "...add ti,ds90c185" to "...add ti, ds90c185"
>>>
>>> You might want to evaluate if that auto-correction "feature" should be
>>> disabled/tweaked/whatever...
>>
>> Hm, weird. I just downloaded the mbox from dri-devel's patchwork and
>> passed it to dim apply. dim tends to do a lot of things behind the
>> scene, so maybe it's also trying to fix typos :-).
>
> Nope, looks like it was already wrong on patchwork [1], don't know what
> happened, because the version I have in my mailbox is correct.
>
> [1]https://patchwork.freedesktop.org/patch/246039/
Apparently a known issue: https://github.com/getpatchwork/patchwork/issues/197
Cheers,
Peter
Powered by blists - more mailing lists