ARM Sunxi Platform Development
 help / color / mirror / Atom feed
From: Jesse Taube <mr.bossman075@gmail.com>
To: devicetree@vger.kernel.org
Cc: robh+dt@kernel.org, Mr.Bossman075@gmail.com,
	andre.przywara@arm.com, linux-sunxi@lists.linux.dev,
	mripard@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/4] ARM: dtsi: suniv: F1c100s add clock and reset macros
Date: Sun, 30 Jan 2022 17:03:22 -0500	[thread overview]
Message-ID: <20220130220325.1983918-1-Mr.Bossman075@gmail.com> (raw)

Include clock and reset macros and replace magic numbers.

Signed-off-by: Jesse Taube <Mr.Bossman075@gmail.com>
---
 arch/arm/boot/dts/suniv-f1c100s.dtsi | 17 ++++++++++-------
 1 file changed, 10 insertions(+), 7 deletions(-)

diff --git a/arch/arm/boot/dts/suniv-f1c100s.dtsi b/arch/arm/boot/dts/suniv-f1c100s.dtsi
index 6100d3b75f61..953228cc8d52 100644
--- a/arch/arm/boot/dts/suniv-f1c100s.dtsi
+++ b/arch/arm/boot/dts/suniv-f1c100s.dtsi
@@ -4,6 +4,9 @@
  * Copyright 2018 Mesih Kilinc <mesihkilinc@gmail.com>
  */
 
+#include <dt-bindings/clock/suniv-ccu-f1c100s.h>
+#include <dt-bindings/reset/suniv-ccu-f1c100s.h>
+
 / {
 	#address-cells = <1>;
 	#size-cells = <1>;
@@ -82,7 +85,7 @@ pio: pinctrl@1c20800 {
 			compatible = "allwinner,suniv-f1c100s-pinctrl";
 			reg = <0x01c20800 0x400>;
 			interrupts = <38>, <39>, <40>;
-			clocks = <&ccu 37>, <&osc24M>, <&osc32k>;
+			clocks = <&ccu CLK_BUS_PIO>, <&osc24M>, <&osc32k>;
 			clock-names = "apb", "hosc", "losc";
 			gpio-controller;
 			interrupt-controller;
@@ -114,8 +117,8 @@ uart0: serial@1c25000 {
 			interrupts = <1>;
 			reg-shift = <2>;
 			reg-io-width = <4>;
-			clocks = <&ccu 38>;
-			resets = <&ccu 24>;
+			clocks = <&ccu CLK_BUS_UART0>;
+			resets = <&ccu RST_BUS_UART0>;
 			status = "disabled";
 		};
 
@@ -125,8 +128,8 @@ uart1: serial@1c25400 {
 			interrupts = <2>;
 			reg-shift = <2>;
 			reg-io-width = <4>;
-			clocks = <&ccu 39>;
-			resets = <&ccu 25>;
+			clocks = <&ccu CLK_BUS_UART1>;
+			resets = <&ccu RST_BUS_UART1>;
 			status = "disabled";
 		};
 
@@ -136,8 +139,8 @@ uart2: serial@1c25800 {
 			interrupts = <3>;
 			reg-shift = <2>;
 			reg-io-width = <4>;
-			clocks = <&ccu 40>;
-			resets = <&ccu 26>;
+			clocks = <&ccu CLK_BUS_UART2>;
+			resets = <&ccu RST_BUS_UART2>;
 			status = "disabled";
 		};
 	};
-- 
2.34.1


             reply	other threads:[~2022-01-30 22:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-30 22:03 Jesse Taube [this message]
2022-01-30 22:03 ` [PATCH v2 2/4] dt-bindings: mmc: sunxi: Add Allwinner F1c100s compatibles Jesse Taube
2022-01-31  9:45   ` Maxime Ripard
2022-01-31 10:19   ` Andre Przywara
2022-02-09 21:15   ` Rob Herring
2022-01-30 22:03 ` [PATCH v2 3/4] ARM: dtsi: suniv: Add mmc to f1c100s dtsi Jesse Taube
2022-01-31  9:46   ` Maxime Ripard
2022-01-31 10:14   ` Andre Przywara
2022-01-30 22:03 ` [PATCH v2 4/4] ARM: dts: suniv: Enable mmc for f1c100s Jesse Taube
2022-01-31  9:46   ` Maxime Ripard
2022-01-31 10:17   ` Andre Przywara
2022-01-31  9:50 ` [PATCH v2 1/4] ARM: dtsi: suniv: F1c100s add clock and reset macros Andre Przywara

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=20220130220325.1983918-1-Mr.Bossman075@gmail.com \
    --to=mr.bossman075@gmail.com \
    --cc=andre.przywara@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=mripard@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