From: Frank Li <Frank.li@nxp.com>
To: Carlos Song <carlos.song@nxp.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
s.hauer@pengutronix.de, shawnguo@kernel.org,
kernel@pengutronix.de, festevam@gmail.com, daniel.baluta@nxp.com,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: imx95: correct I3C2 pclk to IMX95_CLK_BUSWAKEUP
Date: Tue, 18 Nov 2025 11:03:57 -0500 [thread overview]
Message-ID: <aRyY7TIAIJW6nlG8@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20251118062855.1417564-1-carlos.song@nxp.com>
On Tue, Nov 18, 2025 at 02:28:54PM +0800, Carlos Song wrote:
> I3C2 is in WAKEUP domain. Its pclk should be IMX95_CLK_BUSWAKEUP.
>
> Fixes: 969497ebefcf ("arm64: dts: imx95: Add i3c1 and i3c2")
> Signed-off-by: Carlos Song <carlos.song@nxp.com>
> Cc: <stable@vger.kernel.org>
Reviewed-by: Frank Li <Frank.Li@nxp.com>
> ---
> arch/arm64/boot/dts/freescale/imx95.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx95.dtsi b/arch/arm64/boot/dts/freescale/imx95.dtsi
> index e45014d50abe..a4d854817559 100644
> --- a/arch/arm64/boot/dts/freescale/imx95.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx95.dtsi
> @@ -828,7 +828,7 @@ i3c2: i3c@42520000 {
> interrupts = <GIC_SPI 57 IRQ_TYPE_LEVEL_HIGH>;
> #address-cells = <3>;
> #size-cells = <0>;
> - clocks = <&scmi_clk IMX95_CLK_BUSAON>,
> + clocks = <&scmi_clk IMX95_CLK_BUSWAKEUP>,
> <&scmi_clk IMX95_CLK_I3C2SLOW>;
> clock-names = "pclk", "fast_clk";
> status = "disabled";
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-11-18 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 6:28 [PATCH] arm64: dts: imx95: correct I3C2 pclk to IMX95_CLK_BUSWAKEUP Carlos Song
2025-11-18 16:03 ` Frank Li [this message]
2025-12-29 8:30 ` Shawn Guo
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=aRyY7TIAIJW6nlG8@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=carlos.song@nxp.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stable@vger.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