From: "Andreas Färber" <afaerber@suse.de>
To: linux-realtek-soc@lists.infradead.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, "Andreas Färber" <afaerber@suse.de>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: [PATCH v2 10/11] arm64: dts: realtek: Adopt RTD129x reset constants
Date: Wed, 23 Oct 2019 12:13:16 +0200 [thread overview]
Message-ID: <20191023101317.26656-11-afaerber@suse.de> (raw)
In-Reply-To: <20191023101317.26656-1-afaerber@suse.de>
Replace reset controller indices with constants.
Signed-off-by: Andreas Färber <afaerber@suse.de>
---
v1 -> v2: Unchanged
arch/arm64/boot/dts/realtek/rtd129x.dtsi | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/boot/dts/realtek/rtd129x.dtsi b/arch/arm64/boot/dts/realtek/rtd129x.dtsi
index 15d321d9515c..4433114476f5 100644
--- a/arch/arm64/boot/dts/realtek/rtd129x.dtsi
+++ b/arch/arm64/boot/dts/realtek/rtd129x.dtsi
@@ -12,6 +12,7 @@
/memreserve/ 0x0000000001ffe000 0x0000000000004000;
#include <dt-bindings/interrupt-controller/arm-gic.h>
+#include <dt-bindings/reset/realtek,rtd1295.h>
/ {
interrupt-parent = <&gic>;
@@ -79,7 +80,7 @@
reg-shift = <2>;
reg-io-width = <4>;
clock-frequency = <27000000>;
- resets = <&iso_reset 8>;
+ resets = <&iso_reset RTD1295_ISO_RSTN_UR0>;
status = "disabled";
};
@@ -89,7 +90,7 @@
reg-shift = <2>;
reg-io-width = <4>;
clock-frequency = <432000000>;
- resets = <&reset2 28>;
+ resets = <&reset2 RTD1295_RSTN_UR1>;
status = "disabled";
};
@@ -99,7 +100,7 @@
reg-shift = <2>;
reg-io-width = <4>;
clock-frequency = <432000000>;
- resets = <&reset2 27>;
+ resets = <&reset2 RTD1295_RSTN_UR2>;
status = "disabled";
};
--
2.16.4
next prev parent reply other threads:[~2019-10-23 10:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 10:13 [PATCH v2 00/11] arm64: Realtek RTD1295 reset controllers Andreas Färber
2019-10-23 10:13 ` [PATCH v2 01/11] dt-bindings: reset: Add Realtek RTD1295 Andreas Färber
2019-10-29 5:25 ` Andreas Färber
2019-10-23 10:13 ` [PATCH v2 02/11] dt-bindings: reset: Add Realtek RTD1195 Andreas Färber
2019-10-26 0:16 ` Rob Herring
2019-10-23 10:13 ` [PATCH v2 06/11] arm64: dts: realtek: Add RTD129x reset controller nodes Andreas Färber
2019-10-29 5:27 ` Andreas Färber
2019-10-23 10:13 ` [PATCH v2 07/11] arm64: dts: realtek: Add RTD129x UART resets Andreas Färber
2019-10-29 5:28 ` Andreas Färber
2019-10-23 10:13 ` [PATCH v2 08/11] ARM: dts: rtd1195: Add reset nodes Andreas Färber
2019-10-23 10:13 ` [PATCH v2 09/11] ARM: dts: rtd1195: Add UART resets Andreas Färber
2019-10-23 10:13 ` Andreas Färber [this message]
2019-10-29 5:29 ` [PATCH v2 10/11] arm64: dts: realtek: Adopt RTD129x reset constants Andreas Färber
2019-10-23 10:13 ` [PATCH v2 11/11] ARM: dts: rtd1195: Adopt " Andreas Färber
2019-10-24 8:06 ` [PATCH v2 00/11] arm64: Realtek RTD1295 reset controllers Philipp Zabel
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=20191023101317.26656-11-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=mark.rutland@arm.com \
--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).