From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Patrick Rudolph <patrick.rudolph@9elements.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-binding: Add cypress,cy8c95x0 binding
Date: Tue, 19 Apr 2022 13:50:01 +0200 [thread overview]
Message-ID: <f6ea5c51-97dd-b225-3fb7-fcea5f722c39@linaro.org> (raw)
In-Reply-To: <20220419071503.1596423-2-patrick.rudolph@9elements.com>
On 19/04/2022 09:15, Patrick Rudolph wrote:
> Added device tree binding documentation for
> Cypress CY8C95x0 I2C pin-controller.
>
Thank you for your patch. There is something to discuss/improve.
(...)
> + reg:
> + maxItems: 1
> +
> + gpio-controller: true
> +
> + '#gpio-cells':
> + description:
> + The first cell is the pin number and the second cell is used
> + to specify optional parameters.
> + const: 2
> +
> + gpio-reserved-ranges: true
> +
> + interrupts:
> + maxItems: 1
> +
> + interrupt-controller: true
> +
> + '#interrupt-cells':
> + description:
> + Specifies the pin number and flags, as defined in
> + include/dt-bindings/interrupt-controller/irq.h
Skip description, it's obvious.
> + const: 2
> +
> + ngpios:
> + minimum: 1
> + maximum: 60
> +
> + gpio-line-names:
> + minItems: 1
> + maxItems: 60
> +
> + vdd-supply:
> + description:
> + Optional power supply.
> +
> +patternProperties:
> + '-pins$':
> + type: object
> + description:
> + Pinctrl node's client devices use subnodes for desired pin configuration.
> + Client device subnodes use below standard properties.
> + $ref: "/schemas/pinctrl/pincfg-node.yaml"
> +
> + properties:
> + pins:
> + description:
> + List of gpio pins affected by the properties specified in this
> + subnode.
> + items:
> + oneOf:
Why do you need oneOf here?
> + - pattern: "^gp([0-7][0-7])$"
> + minItems: 1
> + maxItems: 60
> +
> + function:
> + enum: [ gpio, pwm ]
> +
No need for blank line. In other cases you put description before the
property constraints, so do it consistently here as well.
> + description:
> + Specify the alternative function to be configured for the specified
> + pins.
> +
> + bias-pull-down: true
> +
> + bias-pull-up: true
> +
> + bias-disable: true
> +
> + output-high: true
> +
> + output-low: true
> +
> + drive-push-pull: true
> +
> + drive-open-drain: true
> +
> + drive-open-source: true
> +
> + required:
> + - pins
> + - function
> +
> + additionalProperties: false
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - interrupt-controller
> + - '#interrupt-cells'
> + - gpio-controller
> + - '#gpio-cells'
no allOf referencing pinctrl.yaml? Include it unless there is some
reason not to.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-19 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 7:14 [PATCH 0/2] Add support for cy8c95x0 pinctrl Patrick Rudolph
2022-04-19 7:15 ` [PATCH 1/2] dt-binding: Add cypress,cy8c95x0 binding Patrick Rudolph
2022-04-19 11:50 ` Krzysztof Kozlowski [this message]
2022-04-21 20:42 ` Linus Walleij
2022-04-19 7:15 ` [PATCH 2/2] pinctrl: Add Cypress cy8c95x0 support Patrick Rudolph
2022-04-21 20:53 ` Linus Walleij
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=f6ea5c51-97dd-b225-3fb7-fcea5f722c39@linaro.org \
--to=krzysztof.kozlowski@linaro.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=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).