Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sander Vanheule <sander@svanheule.net>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Chris Packham <chris.packham@alliedtelesis.co.nz>,
	devicetree@vger.kernel.org, linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Sander Vanheule <sander@svanheule.net>
Subject: [PATCH 7/9] mips: dts: realtek: Replace uart clock property
Date: Sun, 19 Jan 2025 19:34:22 +0100	[thread overview]
Message-ID: <20250119183424.259353-8-sander@svanheule.net> (raw)
In-Reply-To: <20250119183424.259353-1-sander@svanheule.net>

Add a fixed clock to define the clock frequency of the Lexra bus and use
this for the two uart nodes instead of a separate clock-frequency
property.

Signed-off-by: Sander Vanheule <sander@svanheule.net>
---
 arch/mips/boot/dts/realtek/rtl838x.dtsi | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/arch/mips/boot/dts/realtek/rtl838x.dtsi b/arch/mips/boot/dts/realtek/rtl838x.dtsi
index e3183a71765e..246f4f607128 100644
--- a/arch/mips/boot/dts/realtek/rtl838x.dtsi
+++ b/arch/mips/boot/dts/realtek/rtl838x.dtsi
@@ -34,6 +34,12 @@ cpuintc: cpuintc {
 		interrupt-controller;
 	};
 
+	lx_clk: clock-lexra {
+		compatible = "fixed-clock";
+		#clock-cells = <0>;
+		clock-frequency = <200000000>;
+	};
+
 	soc@18000000 {
 		compatible = "simple-bus";
 		#address-cells = <1>;
@@ -44,7 +50,7 @@ uart0: serial@2000 {
 			compatible = "ns16550a";
 			reg = <0x2000 0x100>;
 
-			clock-frequency = <200000000>;
+			clocks = <&lx_clk>;
 
 			interrupt-parent = <&intc>;
 			interrupts = <31>;
@@ -61,7 +67,7 @@ uart1: serial@2100 {
 			compatible = "ns16550a";
 			reg = <0x2100 0x100>;
 
-			clock-frequency = <200000000>;
+			clocks = <&lx_clk>;
 
 			interrupt-parent = <&intc>;
 			interrupts = <30>;
-- 
2.48.1


  parent reply	other threads:[~2025-01-19 18:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-19 18:34 [PATCH 0/9] mips: dts: Split Realtek devicetrees Sander Vanheule
2025-01-19 18:34 ` [PATCH 1/9] mips: dts: realtek: Decouple RTL930x base DTSI Sander Vanheule
2025-01-20  1:20   ` Chris Packham
2025-01-19 18:34 ` [PATCH 2/9] mips: dts: realtek: Clean up CPU clocks Sander Vanheule
2025-01-20  1:21   ` Chris Packham
2025-01-19 18:34 ` [PATCH 3/9] mips: dts: realtek: Add address to SoC node name Sander Vanheule
2025-01-20  1:22   ` Chris Packham
2025-01-19 18:34 ` [PATCH 4/9] mips: dts: realtek: Fold rtl83xx into rtl838x Sander Vanheule
2025-01-20  1:23   ` Chris Packham
2025-01-19 18:34 ` [PATCH 5/9] mips: dts: realtek: Add SoC IRQ node for RTL838x Sander Vanheule
2025-01-19 18:34 ` [PATCH 6/9] mips: dts: realtek: Correct uart interrupt-parent Sander Vanheule
2025-01-19 18:34 ` Sander Vanheule [this message]
2025-01-19 18:34 ` [PATCH 8/9] mips: dts: realtek: Add RTL838x SoC peripherals Sander Vanheule
2025-01-19 18:34 ` [PATCH 9/9] mips: dts: realtek: Add restart to Cisco SG220-26P Sander Vanheule
2025-02-21 15:27 ` [PATCH 0/9] mips: dts: Split Realtek devicetrees Thomas Bogendoerfer
2025-02-22 10:57   ` Sander Vanheule

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=20250119183424.259353-8-sander@svanheule.net \
    --to=sander@svanheule.net \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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