From: Krzysztof Kozlowski <krzk@kernel.org>
To: Troy Mitchell <troymitchell988@gmail.com>,
Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: mfd: add support for P1 from SpacemiT
Date: Mon, 30 Dec 2024 12:27:23 +0100 [thread overview]
Message-ID: <0e66efd9-6507-4c58-8ad5-d27e9e334238@kernel.org> (raw)
In-Reply-To: <20241230-k1-p1-v1-1-aa4e02b9f993@gmail.com>
On 30/12/2024 11:02, Troy Mitchell wrote:
> +
> +properties:
> + compatible:
> + const: spacemit,p1-pmic
spacemit,p1
Unless this can be something else?
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + regulators:
> + type: object
> +
> + properties:
> + compatible:
> + const: pmic,p1-regulator
Drop compatible, regulators are not re-usable blocks.
> +
> + required:
> + - compatible
> +
> + patternProperties:
> + "^(dcdc-reg[1-6]|aldo-reg[1-4]|dldo-reg[1-7]|switch)$":
You can drop all "reg" suffixes.
> + type: object
> + $ref: /schemas/regulator/regulator.yaml#
> + unevaluatedProperties: false
> +
> + unevaluatedProperties: false
> +
> + pinctrl:
pinctrl or gpio?
> + type: object
> +
> + properties:
> + compatible:
> + const: pmic,p1-pinctrl
> +
> + "#gpio-cells":
> + const: 2
> +
> + gpio-controller: true
> +
> + required:
> + - compatible
> + - "#gpio-cells"
> + - gpio-controller
> +
> + unevaluatedProperties: false
No $ref? Then additionalProperties and put it after type: ... but if you
do not have here pinctrl, then just fold the node into parent.
> +
> + pwrkey:
> + type: object
> + $ref: /schemas/input/input.yaml#
> +
> + properties:
> + compatible:
> + const: pmic,p1-pwrkey
> +
> + required:
> + - compatible
No resources here, fold the device into parent.
> +
> + unevaluatedProperties: false
> +
> + rtc:
> + type: object
> + $ref: /schemas/rtc/rtc.yaml#
No resources here, fold the device into parent.
> +
> + properties:
> + compatible:
> + const: pmic,p1-rtc
> +
> + required:
> + - compatible
> +
> + unevaluatedProperties: false
> +
> +
Only one blank line
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +unevaluatedProperties: false
example-schema explains when to use unevaluated/additionalProps.
Best regards,
Krzysztof
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-12-30 11:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 10:02 [PATCH 0/2] Add support for the P1 PMIC from SpacemiT Troy Mitchell
2024-12-30 10:02 ` [PATCH 1/2] dt-bindings: mfd: add support for P1 " Troy Mitchell
2024-12-30 11:22 ` Rob Herring (Arm)
2024-12-30 11:27 ` Krzysztof Kozlowski [this message]
2024-12-30 10:02 ` [PATCH 2/2] mfd: add new driver for P1 PMIC " Troy Mitchell
2024-12-30 10:15 ` Troy Mitchell
2024-12-30 11:33 ` Krzysztof Kozlowski
2024-12-31 7:05 ` Troy Mitchell
2024-12-31 19:42 ` Jure Repinc
2025-01-06 15:43 ` Lee Jones
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=0e66efd9-6507-4c58-8ad5-d27e9e334238@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh@kernel.org \
--cc=troymitchell988@gmail.com \
/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