[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <171985263741.87483.1879777623519602279.robh@kernel.org>
Date: Mon, 1 Jul 2024 10:50:38 -0600
From: "Rob Herring (Arm)" <robh@...nel.org>
To: Nishanth Menon <nm@...com>
Cc: Conor Dooley <conor+dt@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
linux-gpio@...r.kernel.org,
Linus Walleij <linus.walleij@...aro.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, Tony Lindgren <tony@...mide.com>
Subject: Re: [PATCH V2] dt-bindings: pinctrl: pinctrl-single: Fix
pinctrl-single,gpio-range description
On Thu, 27 Jun 2024 10:06:10 -0500, Nishanth Menon wrote:
> The binding is supposed to describe the properties of each element
> of the pinctrl-single,gpio-range array entry, however when we use
> "- items:" instead of "items:", it explicitly describes that there
> is just a single entry in the array.
>
> The pinctrl-single,gpio-range property should describe more than one
> entry in the array. Fix the typo and adjust the alignment of the
> description of the entries appropriately.
>
> Fixes: 677a62482bd6 ("dt-bindings: pinctrl: Update pinctrl-single to use yaml")
> Signed-off-by: Nishanth Menon <nm@...com>
> ---
> Symptom:
> pinctrl-single,gpio-range = <&range 0 21 7>;
> generates no warning
> However,
> pinctrl-single,gpio-range = <&range 0 21 7>, <&range 32 2 7>;
> generates "is too long" warning.
>
> This is just an attempt to fix the binding that is existing.
>
> V1: https://lore.kernel.org/all/20240618165102.2380159-1-nm@ti.com/
>
> Patch is based on next-20240626
>
> .../devicetree/bindings/pinctrl/pinctrl-single.yaml | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
Reviewed-by: Rob Herring (Arm) <robh@...nel.org>
Powered by blists - more mailing lists