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: [RFC PATCH 1/3] dt-bindings: pinctrl: jh7110-sys: add force inputs
Date: Wed, 23 Apr 2025 00:22:48 +0800 [thread overview]
Message-ID: <20250422162250.436169-2-uwu@icenowy.me> (raw)
In-Reply-To: <20250422162250.436169-1-uwu@icenowy.me>
The internal inputs routed by the pin controller could be routed not to
any GPIOs but forced low/high in the pin controller, which is a useful
feature for some input signals (e.g. overcurrent_n pin of the USB
controller, which needs to be tied to high if not externally routed).
Add two properties to support forcing inputs to low/high.
Signed-off-by: Icenowy Zheng <uwu@icenowy.me>
---
.../bindings/pinctrl/starfive,jh7110-sys-pinctrl.yaml | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/devicetree/bindings/pinctrl/starfive,jh7110-sys-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/starfive,jh7110-sys-pinctrl.yaml
index 222b9e240f8af..d793290afdd74 100644
--- a/Documentation/devicetree/bindings/pinctrl/starfive,jh7110-sys-pinctrl.yaml
+++ b/Documentation/devicetree/bindings/pinctrl/starfive,jh7110-sys-pinctrl.yaml
@@ -46,6 +46,16 @@ properties:
'#gpio-cells':
const: 2
+ starfive,force-low-inputs:
+ description:
+ The list of input signals forced to be low inside the SoC itself.
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+
+ starfive,force-high-inputs:
+ description:
+ The list of input signals forced to be high inside the SoC itself.
+ $ref: /schemas/types.yaml#/definitions/uint32-array
+
patternProperties:
'-[0-9]+$':
type: object
--
2.49.0
next prev parent reply other threads:[~2025-04-22 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 16:22 [RFC PATCH 0/3] pinctrl: starfive: jh7110: support " Icenowy Zheng
2025-04-22 16:22 ` Icenowy Zheng [this message]
2025-04-23 9:09 ` [RFC PATCH 1/3] dt-bindings: pinctrl: jh7110-sys: add " Linus Walleij
2025-04-23 9:40 ` Icenowy Zheng
2025-04-23 10:55 ` Linus Walleij
2025-04-23 14:21 ` Icenowy Zheng
2025-04-24 8:48 ` Linus Walleij
2025-04-22 16:22 ` [RFC PATCH 2/3] pinctrl: starfive: jh7110: support forcing inputs to low/high Icenowy Zheng
2025-04-22 16:22 ` [RFC PATCH 3/3] riscv: dts: starfive: jh7110-pine64-star64: force no USB overcurrent Icenowy Zheng
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=20250422162250.436169-2-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
all inboxes | Powered by JetHome®