From: Krzysztof Kozlowski <krzk@kernel.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: linux-gpio@vger.kernel.org, Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Saravana Kannan <saravanak@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: gpio: document gpio-line usage
Date: Sat, 14 Feb 2026 21:53:37 +0100 [thread overview]
Message-ID: <b851bfd4-3c35-489f-a32d-dcd7a37ca99a@kernel.org> (raw)
In-Reply-To: <CADvTj4pRE1LHfPnVbWLpd-AedCgCNWPDjcP=oLHyT=muH4r6=A@mail.gmail.com>
On 14/02/2026 21:45, James Hilliard wrote:
> On Sat, Feb 14, 2026 at 2:07 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On Fri, Feb 13, 2026 at 03:32:02PM -0700, James Hilliard wrote:
>>> Document gpio-line child nodes for GPIO controller initialization
>>> without line hogging.
>>>
>>> Describe gpio-line-name semantics for both gpio-line nodes and gpio-hog
>>> nodes, and update examples accordingly.
>>>
>>> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
>>> ---
>>> .../devicetree/bindings/gpio/gpio.txt | 47 ++++++++++++++-----
>>> 1 file changed, 34 insertions(+), 13 deletions(-)
>>>
>>> diff --git a/Documentation/devicetree/bindings/gpio/gpio.txt b/Documentation/devicetree/bindings/gpio/gpio.txt
>>> index b37dbb1edc62..cf591954eafd 100644
>>> --- a/Documentation/devicetree/bindings/gpio/gpio.txt
>>> +++ b/Documentation/devicetree/bindings/gpio/gpio.txt
>>> @@ -199,28 +199,41 @@ gpio-controller@00000000 {
>>> "poweroff", "reset";
>>> }
>>>
>>> -The GPIO chip may contain GPIO hog definitions. GPIO hogging is a mechanism
>>> -providing automatic GPIO request and configuration as part of the
>>> -gpio-controller's driver probe function.
>>> +The GPIO chip may contain child nodes used for line setup at probe time:
>>> +- gpio-hog: reserves the GPIO line as a hog and configures it.
>>> +- gpio-line: configures the GPIO line without reserving it as a hog.
>>
>> New properties do not go to TXT bindings, so if you want to introduce
>> gpio-line, you need to send a patch or pull request to dtschema.
>
> Like this?:
> https://github.com/devicetree-org/dt-schema/pull/185
>
> So this would just need a dtschema change and no documentation
> changes in the actual kernel tree?
Yes. In the driver commit changelog (under ---) please mention it
depends on dtschema with a link to the dt-schema pull, so Bartosz will
wait with applying.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-14 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 22:32 [PATCH 1/2] gpiolib: of: add gpio-line node support James Hilliard
2026-02-13 22:32 ` [PATCH 2/2] dt-bindings: gpio: document gpio-line usage James Hilliard
2026-02-14 9:07 ` Krzysztof Kozlowski
2026-02-14 20:45 ` James Hilliard
2026-02-14 20:53 ` Krzysztof Kozlowski [this message]
2026-02-14 9:08 ` [PATCH 1/2] gpiolib: of: add gpio-line node support Krzysztof Kozlowski
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=b851bfd4-3c35-489f-a32d-dcd7a37ca99a@kernel.org \
--to=krzk@kernel.org \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=james.hilliard1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=saravanak@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