From: Abel Vesa <abel.vesa@linaro.org>
To: Peng Fan <peng.fan@nxp.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Abel Vesa <abelvesa@kernel.org>, Frank Li <frank.li@nxp.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>,
Sandor Yu <Sandor.yu@nxp.com>
Subject: Re: [PATCH v3 0/6] clock: imx95: Add LVDS/DISPLAY CSR for i.MX94
Date: Tue, 8 Jul 2025 12:20:15 +0300 [thread overview]
Message-ID: <aGzizyLX8HDWsWWm@linaro.org> (raw)
In-Reply-To: <20250707-imx95-blk-ctl-7-1-v3-0-c1b676ec13be@nxp.com>
On 25-07-07 10:24:36, Peng Fan wrote:
> Similar to i.MX95, i.MX94 also has LVDS/DISPLAY CSR to provide
> clock gate for LVDS and DISPLAY Controller. So following same approach
> to add the support, as what have been done for i.MX95.
>
> Patch 1 is to add the binding doc.
> Patch 2 is fixes when supporting i.MX94, but the issues are
> also exposed to i.MX95 even not triggered. No need to rush the
> two patches for 6.16.
> Patch 3 and 4 is to add the clk driver. Patch 3 is almost picked from
> NXP downstream with a minor update. Patch 4 is modified from NXP
> downstream with a few minor patches merged and updated.
> Patch 5 is the dts part to give reviewer a whole view on how it is used.
>
> Thanks for Frank Li helping do NXP internal review for the patchset.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
For some reason, this doesn't apply cleanly.
Can you rebase on 6.16-rc1 and resend?
Thanks,
Abel
next prev parent reply other threads:[~2025-07-08 9:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 2:24 [PATCH v3 0/6] clock: imx95: Add LVDS/DISPLAY CSR for i.MX94 Peng Fan
2025-07-07 2:24 ` [PATCH v3 1/6] dt-bindings: clock: Add support for i.MX94 LVDS/DISPLAY CSR Peng Fan
2025-07-07 5:36 ` Krzysztof Kozlowski
2025-07-07 2:24 ` [PATCH v3 2/6] clk: imx95-blk-ctl: Fix synchronous abort Peng Fan
2025-07-07 2:24 ` [PATCH v3 3/6] clk: imx95-blk-ctl: Rename lvds and displaymix csr blk Peng Fan
2025-07-07 2:24 ` [PATCH v3 4/6] clk: imx95-blk-ctl: Add clock for i.MX94 LVDS/Display CSR Peng Fan
2025-07-07 2:24 ` [PATCH v3 5/6] MAINTAINERS: Update i.MX Clock Entry Peng Fan
2025-07-08 16:34 ` Abel Vesa
2025-07-07 2:24 ` [PATCH v3 6/6] arm64: dts: imx943: Add LVDS/DISPLAY CSR nodes Peng Fan
2025-07-08 12:19 ` Laurentiu Palcu
2025-07-21 13:36 ` Peng Fan
2025-07-08 9:20 ` Abel Vesa [this message]
2025-07-08 13:26 ` [PATCH v3 0/6] clock: imx95: Add LVDS/DISPLAY CSR for i.MX94 Peng Fan
2025-07-21 8:24 ` (subset) " Abel Vesa
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=aGzizyLX8HDWsWWm@linaro.org \
--to=abel.vesa@linaro.org \
--cc=Sandor.yu@nxp.com \
--cc=abelvesa@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=laurentiu.palcu@oss.nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.