From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 3/4] ARM: dts: versatile: Update spi clock name
Date: Fri, 11 Mar 2022 16:06:34 +0530 [thread overview]
Message-ID: <20220311103635.39849-4-singh.kuldeep87k@gmail.com> (raw)
In-Reply-To: <20220311103635.39849-1-singh.kuldeep87k@gmail.com>
SPI clock for pl022 is "sspclk" and meanwhile ARM versatile platform
specify "SSPCLK" as clock name. Even though binding check don't
differentiate the two names, better to keep same convention throughout
i.e sspclk to align with other platforms.
Signed-off-by: Kuldeep Singh <singh.kuldeep87k@gmail.com>
---
v2:
- Separate out patches for various platforms
- Rebase to top
arch/arm/boot/dts/versatile-ab.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/versatile-ab.dts b/arch/arm/boot/dts/versatile-ab.dts
index 79f7cc241282..a520615f4d8d 100644
--- a/arch/arm/boot/dts/versatile-ab.dts
+++ b/arch/arm/boot/dts/versatile-ab.dts
@@ -391,7 +391,7 @@ spi@101f4000 {
reg = <0x101f4000 0x1000>;
interrupts = <11>;
clocks = <&xtal24mhz>, <&pclk>;
- clock-names = "SSPCLK", "apb_pclk";
+ clock-names = "sspclk", "apb_pclk";
};
fpga {
--
2.25.1
next prev parent reply other threads:[~2022-03-11 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 10:36 [PATCH v2 0/4] DT fixes for pl022 for Arm realview, versatile platforms Kuldeep Singh
2022-03-11 10:36 ` [PATCH v2 1/4] ARM: dts: integratorap: Update spi node properties Kuldeep Singh
2022-03-11 10:36 ` [PATCH v2 2/4] ARM: dts: realview: Update spi clock name Kuldeep Singh
2022-03-11 10:36 ` Kuldeep Singh [this message]
2022-03-11 10:36 ` [PATCH v2 4/4] ARM: dts: ste-dbx: " Kuldeep Singh
2022-03-12 5:26 ` [PATCH v2 0/4] DT fixes for pl022 for Arm realview, versatile platforms Kuldeep Singh
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=20220311103635.39849-4-singh.kuldeep87k@gmail.com \
--to=singh.kuldeep87k@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).