From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: "Chen-Yu Tsai" <wenst@chromium.org>,
"Hsin-Yi Wang" <hsinyi@chromium.org>,
"Nícolas F . R . A . Prado" <nfraprado@collabora.com>,
"Heiko Stuebner" <heiko.stuebner@cherry.de>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Chris Morgan" <macromorgan@hotmail.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Sean Wang" <sean.wang@mediatek.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH 3/4] arm64: dts: mediatek: mt7981: add pinctrl
Date: Wed, 21 Feb 2024 11:00:44 +0100 [thread overview]
Message-ID: <770b23ec-7199-4202-888d-6a22b7f4af74@collabora.com> (raw)
In-Reply-To: <20240221073524.20947-4-zajec5@gmail.com>
Il 21/02/24 08:35, Rafał Miłecki ha scritto:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> MT7981 contains on-SoC PIN controller that is also a GPIO provider.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> arch/arm64/boot/dts/mediatek/mt7981b.dtsi | 37 +++++++++++++++++++++++
> 1 file changed, 37 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt7981b.dtsi b/arch/arm64/boot/dts/mediatek/mt7981b.dtsi
> index 4feff3d1c5f4..fdd5c22cfc9c 100644
> --- a/arch/arm64/boot/dts/mediatek/mt7981b.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt7981b.dtsi
> @@ -86,6 +86,43 @@ pwm@10048000 {
> #pwm-cells = <2>;
> };
>
> + pio: pinctrl@11d00000 {
> + compatible = "mediatek,mt7981-pinctrl";
> + reg = <0 0x11d00000 0 0x1000>,
> + <0 0x11c00000 0 0x1000>,
> + <0 0x11c10000 0 0x1000>,
> + <0 0x11d20000 0 0x1000>,
> + <0 0x11e00000 0 0x1000>,
> + <0 0x11e20000 0 0x1000>,
> + <0 0x11f00000 0 0x1000>,
> + <0 0x11f10000 0 0x1000>,
> + <0 0x1000b000 0 0x1000>;
> + reg-names = "gpio", "iocfg_rt", "iocfg_rm", "iocfg_rb", "iocfg_lb",
> + "iocfg_bl", "iocfg_tm", "iocfg_tl", "eint";
> + interrupt-controller;
> + interrupts = <GIC_SPI 225 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-parent = <&gic>;
> + gpio-ranges = <&pio 0 0 56>;
> + gpio-controller;
> + #gpio-cells = <2>;
> + #interrupt-cells = <2>;
> +
> + mdio-pins {
> + mux {
That's board specific. MDIO and SPI0 pins can be used as GPIO instead of,
respectively, ETH and SPI.
Must go to your board devicetree, not here: please move both.
Cheers,
Angelo
> + function = "eth";
> + groups = "smi_mdc_mdio";
> + };
> + };
> +
> + spi0-pins {
> + mux {
> + function = "spi";
> + groups = "spi0", "spi0_wp_hold";
> + };
> + };
> +
> + };
> +
> clock-controller@15000000 {
> compatible = "mediatek,mt7981-ethsys", "syscon";
> reg = <0 0x15000000 0 0x1000>;
next prev parent reply other threads:[~2024-02-21 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 7:35 [PATCH 0/4] dts: mediatek: add Cudy WR3000 V1 wireless router Rafał Miłecki
2024-02-21 7:35 ` [PATCH 1/4] dt-bindings: vendor-prefixes: add Cudy Rafał Miłecki
2024-02-21 8:40 ` Krzysztof Kozlowski
2024-02-21 7:35 ` [PATCH 2/4] dt-bindings: arm64: dts: mediatek: Add Cudy WR3000 V1 router Rafał Miłecki
2024-02-21 8:40 ` Krzysztof Kozlowski
2024-02-21 9:57 ` AngeloGioacchino Del Regno
2024-02-21 7:35 ` [PATCH 3/4] arm64: dts: mediatek: mt7981: add pinctrl Rafał Miłecki
2024-02-21 10:00 ` AngeloGioacchino Del Regno [this message]
2024-02-21 7:35 ` [PATCH 4/4] arm64: dts: mediatek: Add Cudy WR3000 V1 Rafał Miłecki
2024-02-21 10:11 ` AngeloGioacchino Del Regno
2024-02-21 10:18 ` Rafał Miłecki
2024-02-21 10:52 ` AngeloGioacchino Del Regno
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=770b23ec-7199-4202-888d-6a22b7f4af74@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko.stuebner@cherry.de \
--cc=hsinyi@chromium.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=macromorgan@hotmail.com \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=wenst@chromium.org \
--cc=zajec5@gmail.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
all inboxes | Powered by JetHome®