From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>,
tony@atomide.com, Sebastian Reichel <sre@kernel.org>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-kernel@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: mfd: twl: add charger node also for TWL603x
Date: Wed, 18 Sep 2024 12:47:22 +0200 [thread overview]
Message-ID: <c38c9ada-e054-4a14-9265-25065048ae54@kernel.org> (raw)
In-Reply-To: <20240918084132.928295-3-andreas@kemnade.info>
On 18/09/2024 10:41, 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 | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/ti,twl.yaml b/Documentation/devicetree/bindings/mfd/ti,twl.yaml
> index e94b0fd7af0f8..4064a228cb0fc 100644
> --- a/Documentation/devicetree/bindings/mfd/ti,twl.yaml
> +++ b/Documentation/devicetree/bindings/mfd/ti,twl.yaml
> @@ -105,6 +105,11 @@ allOf:
> regulator-initial-mode: false
>
> properties:
> + bci:
charger
> + type: object
additionalProperties: true
Each node must end with additionalProperties or unevaluated. I think you
never tested it, because dtschema reports this.
> + properties:
> + compatible:
> + const: ti,twl6030-charger
> gpadc:
> type: object
> properties:
> @@ -136,6 +141,13 @@ allOf:
> regulator-initial-mode: false
>
> properties:
> + bci:
> + type: object
> + properties:
> + compatible:
> + items:
> + - const: ti,twl6032-charger
> + - const: ti,twl6030-charger
> gpadc:
> type: object
> properties:
> @@ -222,6 +234,12 @@ examples:
> interrupt-controller;
> #interrupt-cells = <1>;
>
> + bci {
> + compatible = "ti,twl6030-charger";
> + interrupts = <2>, <5>;
> + monitored-battery = <&bat>;
One complete example in parent node, so you can drop example from patch #1.
> + };
> +
> gpadc {
> compatible = "ti,twl6030-gpadc";
> interrupts = <6>;
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-18 10:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 8:41 [PATCH 0/3] power: supply: twl6030/32 charger Andreas Kemnade
2024-09-18 8:41 ` [PATCH 1/3] dt-bindings: power: supply: Add TI TWL603X charger Andreas Kemnade
2024-09-18 10:46 ` Krzysztof Kozlowski
2024-09-18 8:41 ` [PATCH 2/3] dt-bindings: mfd: twl: add charger node also for TWL603x Andreas Kemnade
2024-09-18 10:47 ` Krzysztof Kozlowski [this message]
2024-09-18 11:35 ` Andreas Kemnade
2024-09-21 0:51 ` Rob Herring
2024-09-26 7:26 ` Andreas Kemnade
2024-09-18 8:41 ` [PATCH 3/3] power: supply: initial support for TWL6030/32 Andreas Kemnade
2024-09-18 10:43 ` Krzysztof Kozlowski
2024-09-18 12:43 ` Andreas Kemnade
2024-09-18 12:53 ` Krzysztof Kozlowski
2024-09-23 16:29 ` Andreas Kemnade
2024-09-24 8:00 ` Krzysztof Kozlowski
2024-09-18 21:11 ` kernel test robot
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=c38c9ada-e054-4a14-9265-25065048ae54@kernel.org \
--to=krzk@kernel.org \
--cc=andreas@kemnade.info \
--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-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh@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).