From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 2/3] ARM64: dts: Fix GXL periphs pinctrl pull-enable register base
Date: Wed, 24 May 2017 10:39:49 +0200 [thread overview]
Message-ID: <1495615189.14589.3.camel@baylibre.com> (raw)
In-Reply-To: <1495549311-23660-3-git-send-email-narmstrong@baylibre.com>
On Tue, 2017-05-23 at 16:21 +0200, Neil Armstrong wrote:
> The pull-enable register base was wrongly copied from the GXBB pinctrl node,
> but was not used yet.
Reviewed-by: Jerome Brunet <jbrunet@baylibre.com>
>
> Fixes: fb0fe92294a9 ("ARM64: dts: meson-gxl: Add pinctrl nodes")
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
> ---
> ?arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 2 +-
> ?1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi
> b/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi
> index 4871ce5..57fe1f5 100644
> --- a/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi
> +++ b/arch/arm64/boot/dts/amlogic/meson-gxl.dtsi
> @@ -239,7 +239,7 @@
> ? gpio: bank at 4b0 {
> ? reg = <0x0 0x004b0 0x0 0x28>,
> ? ??????<0x0 0x004e8 0x0 0x14>,
> - ??????<0x0 0x00120 0x0 0x14>,
> + ??????<0x0 0x00520 0x0 0x14>,
> ? ??????<0x0 0x00430 0x0 0x40>;
> ? reg-names = "mux", "pull", "pull-enable", "gpio";
> ? gpio-controller;
next prev parent reply other threads:[~2017-05-24 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 14:21 [PATCH 0/3] ARM64: dts: meson: GXBB and GXL pinctrl fixes Neil Armstrong
2017-05-23 14:21 ` [PATCH 1/3] ARM64: dts: meson-gxl: Fix pinctrl periphs gpio-ranges Neil Armstrong
2017-05-24 8:39 ` Jerome Brunet
2017-05-23 14:21 ` [PATCH 2/3] ARM64: dts: Fix GXL periphs pinctrl pull-enable register base Neil Armstrong
2017-05-24 8:39 ` Jerome Brunet [this message]
2017-05-23 14:21 ` [PATCH 3/3] ARM64: dts: Fix GXBB " Neil Armstrong
2017-05-24 8:40 ` Jerome Brunet
2017-05-30 22:07 ` [PATCH 0/3] ARM64: dts: meson: GXBB and GXL pinctrl fixes Kevin Hilman
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=1495615189.14589.3.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=linus-amlogic@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).