From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Liu Ying <victor.liu@nxp.com>
Cc: marex@denx.de, stefan@agner.ch, airlied@gmail.com,
daniel@ffwll.ch, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
krzysztof.kozlowski@linaro.org, LW@karo-electronics.de
Subject: Re: [PATCH v4 0/6] drm: lcdif: Add i.MX93 LCDIF support
Date: Fri, 17 Feb 2023 09:18:00 +0100 [thread overview]
Message-ID: <13207614.uLZWGnKmhe@steina-w> (raw)
In-Reply-To: <20230217065407.2259731-1-victor.liu@nxp.com>
Hi Liu,
Am Freitag, 17. Februar 2023, 07:54:01 CET schrieb Liu Ying:
> Hi,
>
> This patch set aims to add i.MX93 LCDIF display controller support
> in the existing LCDIF DRM driver. The LCDIF embedded in i.MX93 SoC
> is essentially the same to those embedded in i.MX8mp SoC. Through
> internal bridges, i.MX93 LCDIF may drive a MIPI DSI display or a LVDS
> display or a parallel display.
>
> Patch 1/6 adds device tree binding support for i.MX93 LCDIF in the
> existing fsl,lcdif.yaml.
>
> Patch 2/6 drops lcdif->bridge NULL pointer check as a cleanup patch.
>
> Patch 3/6~5/6 prepare for adding i.MX93 LCDIF support step by step.
>
> Patch 6/6 adds i.MX93 LCDIF compatible string as the last step of
> adding i.MX93 LCDIF support.
Thanks for the series. I could test this on my TQMa93xxLA/MBa93xxCA with a
single LVDS display attached, so no DSI or parallel display. Hence I could not
test the bus format and flags checks, but they look okay.
So you can add
Tested-by: Alexander Stein <alexander.stein@ew.tq-group.com>
to the whole series as well.
One thing I noticed is that, sometimes it seems that before probing lcdif my
system completely freezes. Adding some debug output it seems that's during
powering up the IMX93_MEDIABLK_PD_LCDIF power domain there is some race
condition. But adding more more detailed output made the problem go away.
Did you notice something similar? It might be a red hering though.
Best regards,
Alexander
>
> v3->v4:
> * Improve warning message when ignoring invalid LCDIF OF endpoint ids in
> patch 5/6. (Alexander)
> * Use 'new_{c,p}state' instead of 'new_{crtc,plane}_state' in patch 3/6.
> (Alexander)
> * Simplify lcdif_crtc_reset() by calling lcdif_crtc_atomic_destroy_state()
> in patch 3/6. (Alexander)
> * Add '!crtc->state' check in lcdif_crtc_atomic_duplicate_state() in patch
> 3/6. (Alexander)
> * Collect Alexander's R-b tags on patch 1/6, 2/6 and 6/6.
>
> v2->v3:
> * Fix a trivial typo in patch 6/6's commit message.
>
> v1->v2:
> * Add Krzysztof's A-b and Marek's R-b tags on patch 1/6.
> * Split patch 2/2 in v1 into patch 2/6~6/6 in v2. (Marek, Alexander)
> * Drop '!remote ||' from lcdif_attach_bridge(). (Lothar)
> * Add comment on the 'base' member of lcdif_crtc_state structure to
> note it should always be the first member. (Lothar)
> * Drop unneeded 'bridges' member from lcdif_drm_private structure.
> * Drop a comment about bridge input bus format from
> lcdif_crtc_atomic_check().
>
> Liu Ying (6):
> dt-bindings: lcdif: Add i.MX93 LCDIF support
> drm: lcdif: Drop unnecessary NULL pointer check on lcdif->bridge
> drm: lcdif: Determine bus format and flags in ->atomic_check()
> drm: lcdif: Check consistent bus format and flags across first bridges
> drm: lcdif: Add multiple encoders and first bridges support
> drm: lcdif: Add i.MX93 LCDIF compatible string
>
> .../bindings/display/fsl,lcdif.yaml | 7 +-
> drivers/gpu/drm/mxsfb/lcdif_drv.c | 71 ++++++-
> drivers/gpu/drm/mxsfb/lcdif_drv.h | 5 +-
> drivers/gpu/drm/mxsfb/lcdif_kms.c | 198 ++++++++++++------
> 4 files changed, 206 insertions(+), 75 deletions(-)
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2023-02-17 8:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 6:54 [PATCH v4 0/6] drm: lcdif: Add i.MX93 LCDIF support Liu Ying
2023-02-17 6:54 ` [PATCH v4 1/6] dt-bindings: " Liu Ying
2023-02-17 6:54 ` [PATCH v4 2/6] drm: lcdif: Drop unnecessary NULL pointer check on lcdif->bridge Liu Ying
2023-02-17 6:54 ` [PATCH v4 3/6] drm: lcdif: Determine bus format and flags in ->atomic_check() Liu Ying
2023-02-17 8:09 ` Alexander Stein
2023-02-17 6:54 ` [PATCH v4 4/6] drm: lcdif: Check consistent bus format and flags across first bridges Liu Ying
2023-02-17 8:10 ` Alexander Stein
2023-02-17 6:54 ` [PATCH v4 5/6] drm: lcdif: Add multiple encoders and first bridges support Liu Ying
2023-02-17 8:12 ` Alexander Stein
2023-02-17 6:54 ` [PATCH v4 6/6] drm: lcdif: Add i.MX93 LCDIF compatible string Liu Ying
2023-02-17 8:18 ` Alexander Stein [this message]
2023-02-17 8:59 ` [PATCH v4 0/6] drm: lcdif: Add i.MX93 LCDIF support Liu Ying
2023-02-20 8:55 ` Alexander Stein
2023-02-20 10:16 ` Alexander Stein
2023-02-20 12:46 ` Liu Ying
2023-02-20 12:18 ` Rasmus Villemoes
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=13207614.uLZWGnKmhe@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=LW@karo-electronics.de \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
--cc=victor.liu@nxp.com \
/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).