All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms+renesas@verge.net.au>
To: linux-renesas-soc@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	Magnus Damm <magnus.damm@gmail.com>,
	Simon Horman <horms+renesas@verge.net.au>
Subject: [PATCH 2/9] ARM: dts: r8a73a4: update PFC node name to pin-controller
Date: Wed, 26 Apr 2017 12:05:31 +0200	[thread overview]
Message-ID: <20170426100538.22060-3-horms+renesas@verge.net.au> (raw)
In-Reply-To: <20170426100538.22060-1-horms+renesas@verge.net.au>

The device trees for Renesas SoCs use either pfc or pin-controller as the
node name for the PFC device. This patch is intended to take a step towards
unifying the node name used as pin-controller which appears to be the more
generic of the two and thus more in keeping with the DT specs.

My analysis is that this is a user-visible change to the extent that kernel
logs, and sysfs entries change from e6050000.pfc and pfc@e6050000 to
e6050000.pin-controller and pin-controller@e6050000.

Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
 arch/arm/boot/dts/r8a73a4.dtsi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/r8a73a4.dtsi b/arch/arm/boot/dts/r8a73a4.dtsi
index 1f5c9f6dddba..310222634570 100644
--- a/arch/arm/boot/dts/r8a73a4.dtsi
+++ b/arch/arm/boot/dts/r8a73a4.dtsi
@@ -219,7 +219,7 @@
 		power-domains = <&pd_c4>;
 	};
 
-	pfc: pfc@e6050000 {
+	pfc: pin-controller@e6050000 {
 		compatible = "renesas,pfc-r8a73a4";
 		reg = <0 0xe6050000 0 0x9000>;
 		gpio-controller;
-- 
2.12.2.816.g2cccc81164

WARNING: multiple messages have this Message-ID (diff)
From: horms+renesas@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/9] ARM: dts: r8a73a4: update PFC node name to pin-controller
Date: Wed, 26 Apr 2017 12:05:31 +0200	[thread overview]
Message-ID: <20170426100538.22060-3-horms+renesas@verge.net.au> (raw)
In-Reply-To: <20170426100538.22060-1-horms+renesas@verge.net.au>

The device trees for Renesas SoCs use either pfc or pin-controller as the
node name for the PFC device. This patch is intended to take a step towards
unifying the node name used as pin-controller which appears to be the more
generic of the two and thus more in keeping with the DT specs.

My analysis is that this is a user-visible change to the extent that kernel
logs, and sysfs entries change from e6050000.pfc and pfc at e6050000 to
e6050000.pin-controller and pin-controller at e6050000.

Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
 arch/arm/boot/dts/r8a73a4.dtsi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/r8a73a4.dtsi b/arch/arm/boot/dts/r8a73a4.dtsi
index 1f5c9f6dddba..310222634570 100644
--- a/arch/arm/boot/dts/r8a73a4.dtsi
+++ b/arch/arm/boot/dts/r8a73a4.dtsi
@@ -219,7 +219,7 @@
 		power-domains = <&pd_c4>;
 	};
 
-	pfc: pfc at e6050000 {
+	pfc: pin-controller at e6050000 {
 		compatible = "renesas,pfc-r8a73a4";
 		reg = <0 0xe6050000 0 0x9000>;
 		gpio-controller;
-- 
2.12.2.816.g2cccc81164

  parent reply	other threads:[~2017-04-26 10:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 10:05 [PATCH 0/9] ARM: dts: renesas: update PFC node name to pin-controller Simon Horman
2017-04-26 10:05 ` Simon Horman
2017-04-26 10:05 ` [PATCH 1/9] ARM: dts: emev2: " Simon Horman
2017-04-26 10:05   ` Simon Horman
2017-04-26 10:05 ` Simon Horman [this message]
2017-04-26 10:05   ` [PATCH 2/9] ARM: dts: r8a73a4: " Simon Horman
2017-04-26 10:05 ` [PATCH 3/9] ARM: dts: r8a7740: " Simon Horman
2017-04-26 10:05   ` Simon Horman
2017-04-26 10:05 ` [PATCH 4/9] ARM: dts: r8a7778: " Simon Horman
2017-04-26 10:05   ` Simon Horman
2017-04-26 10:05 ` [PATCH 5/9] ARM: dts: r8a7779: " Simon Horman
2017-04-26 10:05   ` Simon Horman
2017-04-26 10:05 ` [PATCH 6/9] ARM: dts: r8a7790: " Simon Horman
2017-04-26 10:05   ` Simon Horman
2017-04-26 10:05 ` [PATCH 7/9] ARM: dts: r8a7791: " Simon Horman
2017-04-26 10:05   ` Simon Horman
2017-04-26 10:05 ` [PATCH 8/9] ARM: dts: r8a7793: " Simon Horman
2017-04-26 10:05   ` Simon Horman
2017-04-26 10:05 ` [PATCH 9/9] ARM: dts: sh73a0: " Simon Horman
2017-04-26 10:05   ` Simon Horman
2017-04-26 11:20 ` [PATCH 0/9] ARM: dts: renesas: " Geert Uytterhoeven
2017-04-26 11:20   ` Geert Uytterhoeven
2017-04-28  5:10   ` Simon Horman
2017-04-28  5:10     ` Simon Horman
2017-05-03  8:11 ` Simon Horman
2017-05-03  8:11   ` Simon Horman

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=20170426100538.22060-3-horms+renesas@verge.net.au \
    --to=horms+renesas@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.