From: Lucas Stach <l.stach@pengutronix.de>
To: Viraj Shah <viraj.shah@linutronix.de>,
shawnguo@kernel.org, s.hauer@pengutronix.de
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
NXP Linux Team <linux-imx@nxp.com>, Peng Fan <peng.fan@nxp.com>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
Philipp Zabel <p.zabel@pengutronix.de>,
Dan Carpenter <dan.carpenter@oracle.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/4] imx8mm display controller power sequence
Date: Mon, 02 May 2022 12:18:39 +0200 [thread overview]
Message-ID: <f91157496327cead5d098a4f37e9f019e526f7c8.camel@pengutronix.de> (raw)
In-Reply-To: <20220502100233.6023-1-viraj.shah@linutronix.de>
Hi Viraj,
Am Montag, dem 02.05.2022 um 12:02 +0200 schrieb Viraj Shah:
> This patch queue addresses the power sequence of the display controller
> of the imx8mm SoC. The sequence mentioned in example code 5 in section
> 5.2.9.5 of reference manual imx-8MMini-yhsc.pdf was not being performed.
> This meant that the display controller was not coming up.
I don't know where you got the idea that the current implementation
doesn't work. Numerous people are using this to get the i.MX8MM display
light up. All you need to do is add the various display pipeline
peripherals into the virtual power-domains provided by the blk-ctrl
driver. The only thing that prevents upstream from having a working
display pipeline is the conversion of the exynos-dsi into a proper
bridge driver, which has just landed upstream and the addition of a few
DT nodes, now that the drivers are getting ready.
Regards,
Lucas
>
> Viraj Shah (4):
> soc: imx: gpcv2: Power sequence for DISP
> soc: imx: imx8m-blk-ctrl: Display Power ON sequence
> soc: imx: imx8m-blk-ctrl: Add reset bits for mipi dsi phy
> arm64: dts: imx8mm.dtsi: Add resets for dispmix power domain.
>
> arch/arm64/boot/dts/freescale/imx8mm.dtsi | 1 +
> drivers/soc/imx/gpcv2.c | 36 +++++++++++++++++++----
> drivers/soc/imx/imx8m-blk-ctrl.c | 9 ++++--
> 3 files changed, 38 insertions(+), 8 deletions(-)
>
prev parent reply other threads:[~2022-05-02 10:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 10:02 Viraj Shah
2022-05-02 10:02 ` [PATCH v1 1/4] soc: imx8mm: gpcv2: Power sequence for DISP Viraj Shah
2022-05-02 10:11 ` Lucas Stach
2022-05-02 10:02 ` [PATCH v1 2/4] soc: imx: imx8m-blk-ctrl: Display Power ON sequence Viraj Shah
2022-05-02 10:12 ` Lucas Stach
2022-05-02 10:02 ` [PATCH v1 3/4] soc: imx: imx8m-blk-ctrl: Add reset bits for mipi dsi phy Viraj Shah
2022-05-02 10:13 ` Lucas Stach
2022-05-02 10:02 ` [PATCH v1 4/4] arm64: dts: imx8mm.dtsi: Add resets for dispmix power domain Viraj Shah
2022-05-02 10:14 ` Lucas Stach
2022-05-02 10:18 ` Lucas Stach [this message]
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=f91157496327cead5d098a4f37e9f019e526f7c8.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=dan.carpenter@oracle.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=viraj.shah@linutronix.de \
/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
all inboxes | Powered by JetHome®