linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: sean.wang@mediatek.com, linus.walleij@linaro.org,
	linux-mediatek@lists.infradead.org
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 6/7] arm64: dts: mt7622: use gpio-ranges to pinctrl device
Date: Mon, 16 Jul 2018 15:36:50 +0200	[thread overview]
Message-ID: <76cde153-74db-101d-84a1-a0a7da679daf@gmail.com> (raw)
In-Reply-To: <e0483accc1e82280492a2f68a90959232ba868f6.1529639050.git.sean.wang@mediatek.com>



On 22/06/18 05:49, sean.wang@mediatek.com wrote:
> From: Sean Wang <sean.wang@mediatek.com>
> 
> Using gpio-ranges property represent which GPIOs correspond to which pins
> on MT7622 pin controllers. For details, we can see section 2.1 of
> Documentation/devicetree/bindings/gpio/gpio.txt to know how to bind pinctrl
> and gpio drivers via the "gpio-ranges" property.
> 
> Signed-off-by: Sean Wang <sean.wang@mediatek.com>

pushed now to v4.18-next/dts64

Thanks

> ---
>  arch/arm64/boot/dts/mediatek/mt7622.dtsi | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm64/boot/dts/mediatek/mt7622.dtsi b/arch/arm64/boot/dts/mediatek/mt7622.dtsi
> index e2c5450..50cb56c 100644
> --- a/arch/arm64/boot/dts/mediatek/mt7622.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt7622.dtsi
> @@ -291,6 +291,7 @@
>  		reg-names = "base", "eint";
>  		gpio-controller;
>  		#gpio-cells = <2>;
> +		gpio-ranges = <&pio 0 0 103>;
>  		interrupt-controller;
>  		interrupts = <GIC_SPI 153 IRQ_TYPE_LEVEL_HIGH>;
>  		interrupt-parent = <&gic>;
> 

  parent reply	other threads:[~2018-07-16 13:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  3:49 [PATCH 1/7] pinctrl: mt7622: fix error path on failing at groups building sean.wang
2018-06-22  3:49 ` [PATCH 2/7] pinctrl: mt7622: fix initialization sequence between eint and gpiochip sean.wang
2018-06-29 12:18   ` Linus Walleij
2018-06-22  3:49 ` [PATCH 3/7] pinctrl: mt7622: fix that pinctrl_claim_hogs cannot work sean.wang
2018-06-29 12:19   ` Linus Walleij
2018-06-22  3:49 ` [PATCH 4/7] pinctrl: mt7622: stop using the deprecated pinctrl_add_gpio_range sean.wang
2018-06-29 12:21   ` Linus Walleij
2018-06-22  3:49 ` [PATCH 5/7] pinctrl: mt7622: fix a kernel panic when gpio-hog is being applied sean.wang
2018-06-29 12:22   ` Linus Walleij
2018-06-22  3:49 ` [PATCH 6/7] arm64: dts: mt7622: use gpio-ranges to pinctrl device sean.wang
2018-06-29 12:22   ` Linus Walleij
2018-07-16 13:36   ` Matthias Brugger [this message]
     [not found] ` <f222c9f488490bd86d35346e725491e1de306ace.1529639050.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2018-06-22  3:49   ` [PATCH 7/7] arm64: dts: mt7622: add earlycon to mt7622-rfb1 board sean.wang-NuS5LvNUpcJWk0Htik3J/w
2018-07-16 13:37     ` Matthias Brugger
2018-06-29 12:17 ` [PATCH 1/7] pinctrl: mt7622: fix error path on failing at groups building Linus Walleij

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=76cde153-74db-101d-84a1-a0a7da679daf@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=sean.wang@mediatek.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 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).