From: Frank Li <Frank.li@nxp.com>
To: Vladimir Zapolskiy <vz@mleia.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Piotr Wojtaszczyk <piotr.wojtaszczyk@timesys.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Kuldeep Singh <singh.kuldeep87k@gmail.com>
Subject: Re: [PATCH] ARM: dts: lpc32xx: Update spi clock properties
Date: Mon, 29 Dec 2025 10:20:25 -0500 [thread overview]
Message-ID: <aVKcOXWW084h5aTC@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20251224045205.1204414-1-vz@mleia.com>
On Wed, Dec 24, 2025 at 06:52:05AM +0200, Vladimir Zapolskiy wrote:
> From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
>
> PL022 binding require two clocks to be defined but NXP LPC32xx platform
> doesn't comply with the bindings and define only one clock i.e apb_pclk.
>
> Update SPI clocks and clocks-names property by adding appropriate clock
> reference to make it compliant with the bindings.
>
> Noteworthy, strictly speaking the change tackles DT ABI by changing
> the order in the list of clock-names property values, however this level
> of impact is considered as acceptable.
>
> Cc: Vladimir Zapolskiy <vz@mleia.com>
> Signed-off-by: Kuldeep Singh <singh.kuldeep87k@gmail.com>
> [vzapolskiy: rebased and minor update to the commit message]
> Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
Reviewed-by: Frank Li <Frank.Li@nxp.com>
> ---
> I do resend the unapplied change from the past, which raised a discussion:
> * https://lore.kernel.org/all/20220311093800.18778-4-singh.kuldeep87k@gmail.com/
>
> A functionally identical change has been sent recently:
> * https://lore.kernel.org/all/20251029202801.3963952-2-Frank.Li@nxp.com/
> ---
> arch/arm/boot/dts/nxp/lpc/lpc32xx.dtsi | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm/boot/dts/nxp/lpc/lpc32xx.dtsi b/arch/arm/boot/dts/nxp/lpc/lpc32xx.dtsi
> index e780451fd335..206c66bdfe41 100644
> --- a/arch/arm/boot/dts/nxp/lpc/lpc32xx.dtsi
> +++ b/arch/arm/boot/dts/nxp/lpc/lpc32xx.dtsi
> @@ -172,8 +172,8 @@ ssp0: spi@20084000 {
> compatible = "arm,pl022", "arm,primecell";
> reg = <0x20084000 0x1000>;
> interrupts = <20 IRQ_TYPE_LEVEL_HIGH>;
> - clocks = <&clk LPC32XX_CLK_SSP0>;
> - clock-names = "apb_pclk";
> + clocks = <&clk LPC32XX_CLK_SSP0>, <&clk LPC32XX_CLK_SSP0>;
> + clock-names = "sspclk", "apb_pclk";
> #address-cells = <1>;
> #size-cells = <0>;
> status = "disabled";
> @@ -196,8 +196,8 @@ ssp1: spi@2008c000 {
> compatible = "arm,pl022", "arm,primecell";
> reg = <0x2008c000 0x1000>;
> interrupts = <21 IRQ_TYPE_LEVEL_HIGH>;
> - clocks = <&clk LPC32XX_CLK_SSP1>;
> - clock-names = "apb_pclk";
> + clocks = <&clk LPC32XX_CLK_SSP1>, <&clk LPC32XX_CLK_SSP1>;
> + clock-names = "sspclk", "apb_pclk";
> #address-cells = <1>;
> #size-cells = <0>;
> status = "disabled";
> --
> 2.43.0
>
prev parent reply other threads:[~2025-12-29 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 4:52 [PATCH] ARM: dts: lpc32xx: Update spi clock properties Vladimir Zapolskiy
2025-12-29 15:20 ` Frank Li [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=aVKcOXWW084h5aTC@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=piotr.wojtaszczyk@timesys.com \
--cc=robh@kernel.org \
--cc=singh.kuldeep87k@gmail.com \
--cc=vz@mleia.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