Re: [PATCH 2/2] dt-bindings: gpio: document gpio-line usage

From: Krzysztof Kozlowski

Date: Sat Feb 14 2026 - 04:07:46 EST


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@xxxxxxxxx>
> ---
> .../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.

Otherwise how do you validate your DTS? How does it pass validation?

Please don't send a code which fails - either on upstream or downstream
DTS.

Best regards,
Krzysztof