From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Naresh Solanki <naresh.solanki@9elements.com>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Patrick Rudolph <patrick.rudolph@9elements.com>
Cc: mazziesaccount@gmail.com, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: pinctrl: cy8x95x0: Minor fix & update
Date: Tue, 30 Jan 2024 13:19:18 +0100 [thread overview]
Message-ID: <b305291e-199d-4a0b-b24e-09910f1eed37@linaro.org> (raw)
In-Reply-To: <20240130120807.460335-1-naresh.solanki@9elements.com>
On 30/01/2024 13:08, Naresh Solanki wrote:
> Update maxItems to 60 for gpio-reserved-ranges to allow multiple gpio
> reserved ranges.
> Add input-enable property to allow configuring a pin as input.
> Rearrange allOf
Why?
> Update example.
>
> Signed-off-by: Naresh Solanki <naresh.solanki@9elements.com>
> ---
> .../bindings/pinctrl/cypress,cy8c95x0.yaml | 28 +++++++++++++++----
> 1 file changed, 23 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/cypress,cy8c95x0.yaml b/Documentation/devicetree/bindings/pinctrl/cypress,cy8c95x0.yaml
> index 7f30ec2f1e54..89ce0cb68834 100644
> --- a/Documentation/devicetree/bindings/pinctrl/cypress,cy8c95x0.yaml
> +++ b/Documentation/devicetree/bindings/pinctrl/cypress,cy8c95x0.yaml
> @@ -45,7 +45,8 @@ properties:
> maxItems: 1
>
> gpio-reserved-ranges:
> - maxItems: 1
> + minItems: 1
> + maxItems: 60
>
> vdd-supply:
> description:
> @@ -85,6 +86,8 @@ patternProperties:
>
> bias-disable: true
>
> + input-enable: true
> +
> output-high: true
>
> output-low: true
> @@ -101,6 +104,9 @@ patternProperties:
>
> additionalProperties: false
>
> +allOf:
> + - $ref: pinctrl.yaml#
> +
That's not a correct placement.
> required:
> - compatible
> - reg
> @@ -112,9 +118,6 @@ required:
>
> additionalProperties: false
>
> -allOf:
> - - $ref: pinctrl.yaml#
> -
> examples:
> - |
> #include <dt-bindings/interrupt-controller/arm-gic.h>
> @@ -133,6 +136,21 @@ examples:
> interrupts = <GIC_SPI 94 IRQ_TYPE_LEVEL_HIGH>;
> interrupt-controller;
> vdd-supply = <&p3v3>;
> - gpio-reserved-ranges = <5 1>;
> + gpio-reserved-ranges = <1 2>, <6 1>, <10 1>, <15 1>;
> +
> + pinctrl-0 = <&U62160_pins>, <&U62160_ipins>;
> + pinctrl-names = "default";
> + U62160_pins: cfg-pins {
> + pins = "gp03", "gp16", "gp20", "gp50", "gp51";
Your indentation is totally broken.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-01-30 12:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 12:08 [PATCH v2] dt-bindings: pinctrl: cy8x95x0: Minor fix & update Naresh Solanki
2024-01-30 12:19 ` Krzysztof Kozlowski [this message]
2024-01-30 12:26 ` Naresh Solanki
2024-01-30 12:31 ` Krzysztof Kozlowski
2024-01-30 12:35 ` Naresh Solanki
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=b305291e-199d-4a0b-b24e-09910f1eed37@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).