[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbGwPyQgVL18iMvUTAvh4XTjo6g3mGT4e_b2aNAjr2obg@mail.gmail.com>
Date: Wed, 23 Apr 2025 11:09:42 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Icenowy Zheng <uwu@...nowy.me>
Cc: Emil Renner Berthing <kernel@...il.dk>, Jianlong Huang <jianlong.huang@...rfivetech.com>,
Hal Feng <hal.feng@...rfivetech.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, linux-gpio@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org
Subject: Re: [RFC PATCH 1/3] dt-bindings: pinctrl: jh7110-sys: add force inputs
Hi Icenowy,
thanks for your patch!
On Tue, Apr 22, 2025 at 6:23 PM Icenowy Zheng <uwu@...nowy.me> wrote:
> + 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
I don't see why you need this hack.
Use the existing per-pin output-low property (see
Documentation/devicetree/bindings/pinctrl/pincfg-node.yaml).
> + 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
Use the existing output-high property.
Now I *know* these two properties are per-pin. That is more talkative
but way easier for users to read.
Then use pincontrol hogs to make sure these configs are set up
at probe.
Yours,
Linus Walleij
Powered by blists - more mailing lists