From: Krzysztof Kozlowski <krzk@kernel.org>
To: Olivier Louvignes <olivier@mgcrea.io>
Cc: Lee Jones <lee@kernel.org>, Chen-Yu Tsai <wens@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
mfd@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] dt-bindings: mfd: x-powers,axp152: Add the AXP2101
Date: Mon, 26 Oct 2026 10:30:02 +0100 [thread overview]
Message-ID: <20261026-brawny-gleaming-grasshopper-813f7d@quoll> (raw)
In-Reply-To: <20261023100401.67592-2-olivier@mgcrea.io>
On Fri, Oct 23, 2026 at 12:03:55PM +0200, Olivier Louvignes wrote:
> The AXP2101's interrupt line is optional, as for the AXP313A and the
> AXP15060: the driver then registers only the regulators. It has no DCDC
> frequency setting.
>
> Signed-off-by: Olivier Louvignes <olivier@mgcrea.io>
> ---
> Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml b/Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml
> index 45f015d63df1..f5e2c8232581 100644
> --- a/Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml
> +++ b/Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml
> @@ -68,6 +68,7 @@ allOf:
> compatible:
> contains:
> enum:
> + - x-powers,axp2101
Why breaking the order? Keep natural sorted.
> - x-powers,axp15060
> - x-powers,axp305
> - x-powers,axp313a
> @@ -84,6 +85,7 @@ allOf:
> enum:
> - x-powers,axp313a
> - x-powers,axp323
> + - x-powers,axp2101
Sorting is broken in original code but you placed it completely odd.
Neither keeping sorting of 3xx variants nor, between 15060 and 717.
What's the logic?
> - x-powers,axp15060
> - x-powers,axp717
>
> @@ -108,6 +110,7 @@ properties:
> - x-powers,axp806
> - x-powers,axp809
> - x-powers,axp813
> + - x-powers,axp2101
Placement of these entries makes no sense.
> - x-powers,axp15060
> - items:
> - const: x-powers,axp228
> --
> 2.39.5
>
next prev parent reply other threads:[~2026-10-26 9:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 10:03 [PATCH 0/7] Add support for the X-Powers AXP2101 PMIC Olivier Louvignes
2026-10-23 10:03 ` [PATCH 1/7] dt-bindings: mfd: x-powers,axp152: Add the AXP2101 Olivier Louvignes
2026-10-26 9:30 ` Krzysztof Kozlowski [this message]
2026-10-26 9:31 ` Krzysztof Kozlowski
2026-10-23 10:03 ` [PATCH 2/7] mfd: axp20x: Add support for " Olivier Louvignes
2026-10-23 10:03 ` [PATCH 3/7] regulator: " Olivier Louvignes
2026-10-23 11:58 ` Mark Brown
2026-10-23 10:03 ` [PATCH 4/7] dt-bindings: power: supply: axp20x-usb-power: Add " Olivier Louvignes
2026-10-26 9:32 ` Krzysztof Kozlowski
2026-10-23 10:03 ` [PATCH 5/7] power: supply: axp20x_usb_power: Add support for " Olivier Louvignes
2026-10-23 10:04 ` [PATCH 6/7] dt-bindings: power: supply: axp20x-battery: Add " Olivier Louvignes
2026-10-26 9:33 ` Krzysztof Kozlowski
2026-10-23 10:04 ` [PATCH 7/7] power: supply: axp20x_battery: Add support for " Olivier Louvignes
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=20261026-brawny-gleaming-grasshopper-813f7d@quoll \
--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=mfd@lists.linux.dev \
--cc=olivier@mgcrea.io \
--cc=robh@kernel.org \
--cc=wens@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
all inboxes | Powered by JetHome®