From: Marek Vasut <marex@denx.de>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org,
dri-devel <dri-devel@lists.freedesktop.org>,
Robert Foss <robert.foss@linaro.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sam Ravnborg <sam@ravnborg.org>,
Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: [PATCH 1/2] dt-bindings: display: bridge: icn6211: Add support for RGB/BGR swap
Date: Mon, 8 Aug 2022 03:57:39 +0200 [thread overview]
Message-ID: <4788af3e-b36d-fbe9-bd17-db1db85f1b7f@denx.de> (raw)
In-Reply-To: <CAL_JsqLHKnL80spDSAqMq0cOkVNztv0MjVsR-Rs83qd_q7_MQg@mail.gmail.com>
On 8/4/22 00:41, Rob Herring wrote:
> On Tue, Aug 2, 2022 at 5:33 AM Marek Vasut <marex@denx.de> wrote:
>>
>> On 8/1/22 18:32, Rob Herring wrote:
>>> On Mon, Aug 01, 2022 at 03:19:00PM +0200, Marek Vasut wrote:
>>>> The ICN6211 is capable of swapping the output DPI RGB/BGR color channels,
>>>> document a DT property to select this swap in DT. This can be useful on
>>>> hardware where such swap happens.
>>>
>>> We should ensure this series[1] works for you instead.
>>
>> [...]
>>
>>> Rob
>>>
>>> [1] https://lore.kernel.org/r/20220628181838.2031-3-max.oss.09@gmail.com
>>
>> I'm still not convinced that we should encode this pixel format value
>> directly into the DT instead of trying to describe the DPI bus color
>> channel width/order/shift in the DT instead. I think I mentioned that
>> before in one of the previous versions of that series.
>
> I worry that it gets pretty verbose, but worth having the discussion.
> In any case, let's have that discussion and not add yet another one
> off property.
Done, I replied
next prev parent reply other threads:[~2022-08-08 1:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 13:19 [PATCH 1/2] dt-bindings: display: bridge: icn6211: Add support for RGB/BGR swap Marek Vasut
2022-08-01 13:19 ` [PATCH 2/2] drm: " Marek Vasut
2022-08-01 16:32 ` [PATCH 1/2] dt-bindings: display: " Rob Herring
2022-08-02 11:33 ` Marek Vasut
2022-08-03 22:41 ` Rob Herring
2022-08-08 1:57 ` Marek Vasut [this message]
2022-08-26 11:52 ` Linus Walleij
2022-08-26 11:54 ` Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4788af3e-b36d-fbe9-bd17-db1db85f1b7f@denx.de \
--to=marex@denx.de \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jagan@amarulasolutions.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=robert.foss@linaro.org \
--cc=robh@kernel.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).