From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Shengyu Qu <wiagn233@outlook.com>,
lee@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, wens@csie.org,
lgirdwood@gmail.com, broonie@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/4] dt-bindings: mfd: x-powers,axp152: Document the AXP15060 variant
Date: Mon, 10 Apr 2023 19:27:56 +0200 [thread overview]
Message-ID: <ffe813e4-e3ad-3dff-b8e5-42b0f82faed3@linaro.org> (raw)
In-Reply-To: <TY3P286MB26117891DFB2DD615A7C54EF98969@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM>
On 07/04/2023 16:18, Shengyu Qu wrote:
> The X-Powers AXP15060 is a PMIC seen on Starfive Visionfive 2 board. Add
> relative compatible item and CPUSLDO support for it.
>
> Signed-off-by: Shengyu Qu <wiagn233@outlook.com>
> ---
> Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml | 3 ++-
I received cover letter disattached from rest of patchset and everything
duplicate. Please check your process of sending patches.
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml b/Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml
> index b7a8747d5fa0..e150a8bf040a 100644
> --- a/Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml
> +++ b/Documentation/devicetree/bindings/mfd/x-powers,axp152.yaml
> @@ -92,6 +92,7 @@ properties:
> - x-powers,axp806
> - x-powers,axp809
> - x-powers,axp813
> + - x-powers,axp15060
So you have chosen order by absolute number, not alphabetically. That's
fine, but keep it for the future entries as well. :)
> - items:
> - const: x-powers,axp228
> - const: x-powers,axp221
> @@ -260,7 +261,7 @@ properties:
> Defines the work frequency of DC-DC in kHz.
>
> patternProperties:
> - "^(([a-f])?ldo[0-9]|dcdc[0-7a-e]|ldo(_|-)io(0|1)|(dc1)?sw|rtc(_|-)ldo|drivevbus|dc5ldo)$":
> + "^(([a-f])?ldo[0-9]|dcdc[0-7a-e]|ldo(_|-)io(0|1)|cpusldo|(dc1)?sw|rtc(_|-)ldo|drivevbus|dc5ldo)$":
It seems fixed strings are at the end of entire pattern, so "cpusldo"
should be before "drivevbus".
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-04-10 17:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230407141813.89-1-wiagn233@outlook.com>
2023-04-07 14:18 ` [PATCH v1 1/4] dt-bindings: mfd: x-powers,axp152: Document the AXP15060 variant Shengyu Qu
2023-04-10 17:27 ` Krzysztof Kozlowski [this message]
2023-04-10 17:43 ` Shengyu Qu
2023-04-07 14:18 ` [PATCH v1 2/4] mfd: axp20x: Add support for AXP15060 PMIC Shengyu Qu
2023-04-17 14:05 ` Andre Przywara
2023-04-17 16:21 ` Shengyu Qu
2023-04-07 14:18 ` [PATCH v1 3/4] regulator: axp20x: Add AXP15060 support Shengyu Qu
2023-04-17 14:18 ` Andre Przywara
2023-04-17 16:01 ` Shengyu Qu
2023-04-18 21:57 ` Andre Przywara
2023-04-07 14:18 ` [PATCH v1 4/4] regulator: axp20x: Set DCDC frequency only when property exists Shengyu Qu
2023-04-17 14:20 ` Andre Przywara
2023-04-17 16:31 ` Shengyu Qu
[not found] <20230407135717.17381-1-wiagn233@outlook.com>
2023-04-07 13:57 ` [PATCH v1 1/4] dt-bindings: mfd: x-powers,axp152: Document the AXP15060 variant Shengyu Qu
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=ffe813e4-e3ad-3dff-b8e5-42b0f82faed3@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.org \
--cc=wiagn233@outlook.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).