From: Matthias Brugger <matthias.bgg@gmail.com>
To: Frank Wunderlich <linux@fw-web.de>, linux-mediatek@lists.infradead.org
Cc: Frank Wunderlich <frank-w@public-files.de>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm: dts: mt7623: add otg nodes for bpi-r2
Date: Mon, 20 Sep 2021 14:01:45 +0200 [thread overview]
Message-ID: <a55fca55-78d3-554a-4ad0-f555beac3fa8@gmail.com> (raw)
In-Reply-To: <20210830145958.108605-1-linux@fw-web.de>
On 30/08/2021 16:59, Frank Wunderlich wrote:
> From: Frank Wunderlich <frank-w@public-files.de>
>
> Add OTG-Nodes for BananaPi-R2
>
> Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
Applied to v5.15-next/dts32
Thanks
> ---
> patch is based on
>
> "arm: dts: mt7623: add musb device nodes"
>
> https://patchwork.kernel.org/project/linux-mediatek/patch/20210822041333.5264-2-mans0n@gorani.run/
> ---
> v2:
> rebase on plain 5.14, v1 was based on some not upstreamed work
> ---
> arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts | 25 +++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts b/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
> index e96aa0ed1ebd..027c1b0c6a98 100644
> --- a/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
> +++ b/arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts
> @@ -366,6 +366,14 @@ &pcie1_phy {
> status = "okay";
> };
>
> +&pio {
> + musb_pins: musb {
> + pins-musb {
> + pinmux = <MT7623_PIN_237_EXT_SDIO2_FUNC_DRV_VBUS>;
> + };
> + };
> +};
> +
> &pwm {
> pinctrl-names = "default";
> pinctrl-0 = <&pwm_pins_a>;
> @@ -396,6 +404,19 @@ &uart2 {
> status = "okay";
> };
>
> +&usb0 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&musb_pins>;
> + status = "okay";
> + usb-role-switch;
> +
> + connector {
> + compatible = "gpio-usb-b-connector", "usb-b-connector";
> + type = "micro";
> + id-gpios = <&pio 44 GPIO_ACTIVE_HIGH>;
> + };
> +};
> +
> &usb1 {
> vusb33-supply = <®_3p3v>;
> vbus-supply = <®_5v>;
> @@ -408,6 +429,10 @@ &usb2 {
> status = "okay";
> };
>
> +&u2phy1 {
> + status = "okay";
> +};
> +
> &u3phy1 {
> status = "okay";
> };
>
prev parent reply other threads:[~2021-09-20 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 14:59 [PATCH v2] arm: dts: mt7623: add otg nodes for bpi-r2 Frank Wunderlich
2021-09-20 12:01 ` Matthias Brugger [this message]
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=a55fca55-78d3-554a-4ad0-f555beac3fa8@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@fw-web.de \
--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;
as well as URLs for NNTP newsgroup(s).