[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <76cde153-74db-101d-84a1-a0a7da679daf@gmail.com>
Date: Mon, 16 Jul 2018 15:36:50 +0200
From: Matthias Brugger <matthias.bgg@...il.com>
To: sean.wang@...iatek.com, linus.walleij@...aro.org,
linux-mediatek@...ts.infradead.org
Cc: linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 6/7] arm64: dts: mt7622: use gpio-ranges to pinctrl device
On 22/06/18 05:49, sean.wang@...iatek.com wrote:
> From: Sean Wang <sean.wang@...iatek.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@...iatek.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>;
>
Powered by blists - more mailing lists