Fixes the clock Device ID's in the DT according to the tisci docs clock
identifiers for AM62x
Fixes: c37c58fdeb8a ("arm64: dts: ti: k3-am62: Add more peripheral nodes")
Reviewed-by: Bryan Brattlof <[email protected]>
Signed-off-by: Dhruva Gole <[email protected]>
---
For reference, TISCI Docs: clock id's for AM62
https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/am62x/clocks.html
v3: Rebase on top of linux-next master
v2:
https://lore.kernel.org/linux-devicetree/[email protected]/
v1:
https://lore.kernel.org/linux-devicetree/[email protected]/
arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
index 072903649d6e..ae1ec58117c3 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
@@ -413,7 +413,7 @@ main_spi0: spi@20100000 {
#address-cells = <1>;
#size-cells = <0>;
power-domains = <&k3_pds 141 TI_SCI_PD_EXCLUSIVE>;
- clocks = <&k3_clks 172 0>;
+ clocks = <&k3_clks 141 0>;
status = "disabled";
};
@@ -424,7 +424,7 @@ main_spi1: spi@20110000 {
#address-cells = <1>;
#size-cells = <0>;
power-domains = <&k3_pds 142 TI_SCI_PD_EXCLUSIVE>;
- clocks = <&k3_clks 173 0>;
+ clocks = <&k3_clks 142 0>;
status = "disabled";
};
@@ -435,7 +435,7 @@ main_spi2: spi@20120000 {
#address-cells = <1>;
#size-cells = <0>;
power-domains = <&k3_pds 143 TI_SCI_PD_EXCLUSIVE>;
- clocks = <&k3_clks 174 0>;
+ clocks = <&k3_clks 143 0>;
status = "disabled";
};
--
2.25.1
Hi Dhruva Gole,
On Tue, 3 Jan 2023 11:18:40 +0530, Dhruva Gole wrote:
> Fixes the clock Device ID's in the DT according to the tisci docs clock
> identifiers for AM62x
>
>
I have applied the following to branch ti-k3-next on [1].
Thank you!
[1/1] arm64: dts: ti: k3-am62-main: Fix clocks for McSPI
commit: 6be5d8e5d1804eb4cec29cd8a85dc9cb18683b5d
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh