From: Rob Herring <robh@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: Sebastian Reichel <sre@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
tony@atomide.com, linux-kernel@vger.kernel.org,
khilman@baylibre.com, linux-pm@vger.kernel.org,
linux-omap@vger.kernel.org, Lee Jones <lee@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 2/4] dt-bindings: mfd: twl: add charger node also for TWL603x
Date: Sat, 5 Oct 2024 13:57:21 -0500 [thread overview]
Message-ID: <20241005185721.GA524539-robh@kernel.org> (raw)
In-Reply-To: <20241005060511.1334049-3-andreas@kemnade.info>
On Sat, Oct 05, 2024 at 08:05:09AM +0200, Andreas Kemnade wrote:
> Also the TWL603X devices have a charger, so allow to specify it here.
>
> Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
> ---
> .../devicetree/bindings/mfd/ti,twl.yaml | 30 +++++++++++++++++--
> 1 file changed, 28 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/mfd/ti,twl.yaml b/Documentation/devicetree/bindings/mfd/ti,twl.yaml
> index e94b0fd7af0f8..e772d13adbfdc 100644
> --- a/Documentation/devicetree/bindings/mfd/ti,twl.yaml
> +++ b/Documentation/devicetree/bindings/mfd/ti,twl.yaml
> @@ -54,7 +54,7 @@ allOf:
> $ref: /schemas/iio/adc/ti,twl4030-madc.yaml
> unevaluatedProperties: false
>
> - bci:
> + charger:
> type: object
> $ref: /schemas/power/supply/twl4030-charger.yaml
> unevaluatedProperties: false
> @@ -105,6 +105,11 @@ allOf:
> regulator-initial-mode: false
>
> properties:
> + charger:
> + type: object
> + properties:
> + compatible:
> + const: ti,twl6030-charger
> gpadc:
> type: object
> properties:
> @@ -136,6 +141,13 @@ allOf:
> regulator-initial-mode: false
>
> properties:
> + charger:
> + type: object
> + properties:
> + compatible:
> + items:
> + - const: ti,twl6032-charger
> + - const: ti,twl6030-charger
> gpadc:
> type: object
> properties:
> @@ -169,6 +181,12 @@ properties:
> "#clock-cells":
> const: 1
>
> + charger:
> + type: object
> + additionalProperties: true
> + properties:
> + compatible: true
I think the behavior you're after is:
required:
- compatible
Because what you have is true when compatible is not present.
With that,
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2024-10-05 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 6:05 [PATCH v3 0/4] power: supply: twl6030/32 charger Andreas Kemnade
2024-10-05 6:05 ` [PATCH v3 1/4] dt-bindings: power: supply: Add TI TWL603X charger Andreas Kemnade
2024-10-05 6:05 ` [PATCH v3 2/4] dt-bindings: mfd: twl: add charger node also for TWL603x Andreas Kemnade
2024-10-05 18:57 ` Rob Herring [this message]
2024-10-05 6:05 ` [PATCH v3 3/4] power: supply: initial support for TWL6030/32 Andreas Kemnade
2024-10-05 6:05 ` [PATCH v3 4/4] ARM: dts: ti/omap: use standard node name for twl4030 charger Andreas Kemnade
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=20241005185721.GA524539-robh@kernel.org \
--to=robh@kernel.org \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).