From: Lucas Tanure <tanure@linux.com>
To: Huqiang Qin <huqiang.qin@amlogic.com>,
linus.walleij@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
neil.armstrong@linaro.org, khilman@baylibre.com,
jbrunet@baylibre.com, martin.blumenstingl@googlemail.com,
brgl@bgdev.pl, andy@kernel.org
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 3/3] arm64: dts: Add pinctrl node for Amlogic T7 SoCs
Date: Wed, 27 Sep 2023 07:08:19 +0100 [thread overview]
Message-ID: <ab5d0544-b613-42c1-9b20-ab26c3785175@linux.com> (raw)
In-Reply-To: <20230922094342.637251-4-huqiang.qin@amlogic.com>
On 22-09-2023 10:43, Huqiang Qin wrote:
> Add pinctrl device.
>
> Signed-off-by: Huqiang Qin <huqiang.qin@amlogic.com>
> Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
> ---
>
> V1 -> V2: Unchanged.
> V2 -> V3: Unchanged.
>
> arch/arm64/boot/dts/amlogic/amlogic-t7.dtsi | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/amlogic/amlogic-t7.dtsi b/arch/arm64/boot/dts/amlogic/amlogic-t7.dtsi
> index dae3465bd39b..a03c7667d2b6 100644
> --- a/arch/arm64/boot/dts/amlogic/amlogic-t7.dtsi
> +++ b/arch/arm64/boot/dts/amlogic/amlogic-t7.dtsi
> @@ -155,6 +155,22 @@ watchdog@2100 {
> clocks = <&xtal>;
> };
>
> + periphs_pinctrl: pinctrl@4000 {
> + compatible = "amlogic,t7-periphs-pinctrl";
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges;
> +
> + gpio: bank@4000 {
> + reg = <0x0 0x4000 0x0 0x0064>,
> + <0x0 0x40c0 0x0 0x0220>;
> + reg-names = "mux", "gpio";
> + gpio-controller;
> + #gpio-cells = <2>;
> + gpio-ranges = <&periphs_pinctrl 0 0 157>;
> + };
> + };
> +
> uart_a: serial@78000 {
> compatible = "amlogic,t7-uart", "amlogic,meson-s4-uart";
> reg = <0x0 0x78000 0x0 0x18>;
Tested-by: Lucas Tanure <tanure@linux.com>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-09-27 6:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 9:43 [PATCH V3 0/3] Add pinctrl driver support for Amlogic T7 SoCs Huqiang Qin
2023-09-22 9:43 ` [PATCH V3 1/3] dt-bindings: pinctrl: Add " Huqiang Qin
2023-09-27 6:08 ` Lucas Tanure
2023-09-27 7:48 ` Krzysztof Kozlowski
2023-09-27 10:54 ` Lucas Tanure
2023-09-28 4:56 ` Krzysztof Kozlowski
2023-09-22 9:43 ` [PATCH V3 2/3] pinctrl: Add driver " Huqiang Qin
2023-09-27 6:08 ` Lucas Tanure
2023-09-22 9:43 ` [PATCH V3 3/3] arm64: dts: Add pinctrl node " Huqiang Qin
2023-09-27 6:08 ` Lucas Tanure [this message]
2023-09-25 13:51 ` [PATCH V3 0/3] Add pinctrl driver support " Linus Walleij
2023-10-02 7:01 ` (subset) " Neil Armstrong
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=ab5d0544-b613-42c1-9b20-ab26c3785175@linux.com \
--to=tanure@linux.com \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=huqiang.qin@amlogic.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.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