From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/9] ARM: dts: renesas: update PFC node name to pin-controller
Date: Wed, 3 May 2017 10:11:31 +0200 [thread overview]
Message-ID: <20170503081131.GA28564@verge.net.au> (raw)
In-Reply-To: <20170426100538.22060-1-horms+renesas@verge.net.au>
On Wed, Apr 26, 2017 at 12:05:29PM +0200, Simon Horman wrote:
>
> 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 XXX.pfc and pfc at XXX to
> XXX.pin-controller and pin-controller at XXX.
>
> Boot tested on:
> r8a73a4/ape6evm
> r8a7740/armadillo800evb
> r8a7778/bockw
> r8a7790/lager
> r8a7791/koelsch
> r8a7791/porter
> r8a7793/gose
> sh73a9/kzm9g
>
> Not tested on (due to lack of hw access):
> evm2/kzm9d
> r8a7789/marzen
I have now tested this on r8a7789/marzen
prev parent reply other threads:[~2017-05-03 8:11 UTC|newest]
Thread overview: 13+ 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 ` [PATCH 1/9] ARM: dts: emev2: " Simon Horman
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 ` [PATCH 4/9] ARM: dts: r8a7778: " Simon Horman
2017-04-26 10:05 ` [PATCH 5/9] ARM: dts: r8a7779: " Simon Horman
2017-04-26 10:05 ` [PATCH 6/9] ARM: dts: r8a7790: " Simon Horman
2017-04-26 10:05 ` [PATCH 7/9] ARM: dts: r8a7791: " Simon Horman
2017-04-26 10:05 ` [PATCH 8/9] ARM: dts: r8a7793: " Simon Horman
2017-04-26 10:05 ` [PATCH 9/9] ARM: dts: sh73a0: " Simon Horman
2017-04-26 11:20 ` [PATCH 0/9] ARM: dts: renesas: " Geert Uytterhoeven
2017-04-28 5:10 ` Simon Horman
2017-05-03 8:11 ` Simon Horman [this message]
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=20170503081131.GA28564@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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).