From: Icenowy Zheng <uwu@icenowy.me>
To: Emil Renner Berthing <kernel@esmil.dk>,
Jianlong Huang <jianlong.huang@starfivetech.com>,
Hal Feng <hal.feng@starfivetech.com>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Icenowy Zheng <uwu@icenowy.me>
Subject: [PATCH v2 3/3] riscv: dts: starfive: jh7110-pine64-star64: force no USB overcurrent
Date: Thu, 24 Apr 2025 14:21:54 +0800 [thread overview]
Message-ID: <20250424062154.655128-1-uwu@icenowy.me> (raw)
In-Reply-To: <20250424062017.652969-1-uwu@icenowy.me>
The Star64 board has no GPIOs to indicate USB overcurrent, however the
USB controller would stop to work if the overcurrent_n signal it gets is
low (which means overcurrent situations happening because of the _n).
Use the pin controller to force the overcurrent_n signal to be high in
order to ensure stable behavior of the USB controller.
Signed-off-by: Icenowy Zheng <uwu@icenowy.me>
---
This patch depends on [1] for including the necessary header file.
[1] https://lore.kernel.org/linux-riscv/20250424060605.638678-1-uwu@icenowy.me/T/#u
arch/riscv/boot/dts/starfive/jh7110-pine64-star64.dts | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/riscv/boot/dts/starfive/jh7110-pine64-star64.dts b/arch/riscv/boot/dts/starfive/jh7110-pine64-star64.dts
index 31e825be2065a..4fb522d127e21 100644
--- a/arch/riscv/boot/dts/starfive/jh7110-pine64-star64.dts
+++ b/arch/riscv/boot/dts/starfive/jh7110-pine64-star64.dts
@@ -91,6 +91,13 @@ GPOEN_ENABLE,
input-schmitt-disable;
slew-rate = <0>;
};
+
+ overcurrent-pins {
+ pinmux = <GPIOMUX(PAD_INTERNAL_HIGH,
+ GPOUT_LOW,
+ GPOEN_DISABLE,
+ GPI_SYS_USB_OVERCURRENT)>;
+ };
};
};
--
2.49.0
next prev parent reply other threads:[~2025-04-24 6:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 6:20 [PATCH v2 0/3] pinctrl: starfive: jh7110: support force inputs Icenowy Zheng
2025-04-24 6:20 ` [PATCH v2 1/3] dt-bindings: pinctrl: starfive,jh7110: add PAD_INTERNAL_* virtual pins Icenowy Zheng
2025-04-24 8:15 ` E Shattow
2025-04-25 8:43 ` Icenowy Zheng
2025-04-24 8:51 ` Linus Walleij
2025-04-24 9:38 ` Icenowy Zheng
2025-04-24 10:30 ` Linus Walleij
2025-04-24 12:25 ` Icenowy Zheng
2025-04-28 14:18 ` Linus Walleij
2025-04-28 7:20 ` Krzysztof Kozlowski
2025-04-28 8:40 ` Icenowy Zheng
2025-04-29 7:31 ` Krzysztof Kozlowski
2025-04-29 9:00 ` Icenowy Zheng
2025-04-30 7:21 ` Krzysztof Kozlowski
2025-04-24 6:20 ` [PATCH v2 2/3] pinctrl: starfive: jh7110: add support for PAD_INTERNAL_* for GPI Icenowy Zheng
2025-04-24 7:57 ` E Shattow
2025-05-06 8:10 ` Icenowy Zheng
2025-04-24 6:21 ` Icenowy Zheng [this message]
2025-04-25 9:22 ` [PATCH v2 3/3] riscv: dts: starfive: jh7110-pine64-star64: force no USB overcurrent kernel test robot
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=20250424062154.655128-1-uwu@icenowy.me \
--to=uwu@icenowy.me \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hal.feng@starfivetech.com \
--cc=jianlong.huang@starfivetech.com \
--cc=kernel@esmil.dk \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh@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