From: Denys Drozdov <denys.drozdov@toradex.com>
To: Christoph Niedermaier <cniedermaier@dh-electronics.com>,
dri-devel@lists.freedesktop.org
Cc: Marek Vasut <marex@denx.de>, David Airlie <airlied@linux.ie>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sam Ravnborg <sam@ravnborg.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-arm-kernel@lists.infradead.org,
NXP Linux Team <linux-imx@nxp.com>
Subject: Re: [RFC][PATCH] Revert "drm/panel-simple: drop use of data-mapping property"
Date: Wed, 2 Feb 2022 17:54:08 +0200 [thread overview]
Message-ID: <65ccf910-013e-41e1-5962-032a4da7e06c@toradex.com> (raw)
In-Reply-To: <5374a438-ac8b-05f4-9913-f918ed6aa8c0@toradex.com>
> On 2/1/22 1:07 PM, Christoph Niedermaier wrote:
>> Without the data-mapping devicetree property my display won't
>> work properly. It is flickering, because the bus flags won't
>> be assigned without a defined bus format by the imx parallel
>> display driver. There was a discussion about the removal [1]
>> and an agreement that a better solution is needed, but it is
>> missing so far.
> Obviously bus format in panel-dpi is broken, so this revert
> looks necessary. The current state of panel-dpi isn't consistent
> with changes introduced in commit 4a1d0dbc8332231d1d500d7a1d13c45457262a97
>> So what would be the better approach?
> Another approach is using panel instead of panel-dpi.
>> [1]https://patchwork.freedesktop.org/patch/357659/?series=74705&rev=1
>>
>> This reverts commit d021d751c14752a0266865700f6f212fab40a18c.
> But, also you need to revert 99f155d0776fb8838e326efce056aa08e25433d0
>> Signed-off-by: Christoph Niedermaier<cniedermaier@dh-electronics.com>
> Tested-by: Denys Drozdov<denys.drozdov@toradex.com>
next prev parent reply other threads:[~2022-02-02 17:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 11:07 [RFC][PATCH] Revert "drm/panel-simple: drop use of data-mapping property" Christoph Niedermaier
2022-02-02 15:42 ` Denys Drozdov
2022-02-02 15:54 ` Denys Drozdov [this message]
2022-02-02 23:45 ` Laurent Pinchart
2022-02-03 8:01 ` (EXT) " Alexander Stein
2022-02-08 21:27 ` Christoph Niedermaier
2022-02-08 23:52 ` Marek Vasut
2022-02-09 13:14 ` Max Krummenacher
2022-02-19 9:37 ` Christoph Niedermaier
2022-02-22 8:51 ` Max
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=65ccf910-013e-41e1-5962-032a4da7e06c@toradex.com \
--to=denys.drozdov@toradex.com \
--cc=airlied@linux.ie \
--cc=cniedermaier@dh-electronics.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=marex@denx.de \
--cc=s.hauer@pengutronix.de \
--cc=sam@ravnborg.org \
--cc=shawnguo@kernel.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