From: Krzysztof Kozlowski <krzk@kernel.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>,
ulf.hansson@linaro.org, robh+dt@kernel.org, huziji@marvell.com,
andrew@lunn.ch, gregory.clement@bootlin.com,
sebastian.hesselbarth@gmail.com
Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 3/3] dt-bindings: mmc: xenon: add marvell,sdhci-xenon compatible
Date: Fri, 25 Mar 2022 13:04:11 +0100 [thread overview]
Message-ID: <475d2af6-38cd-47a1-61b2-6b1298bf505d@kernel.org> (raw)
In-Reply-To: <20220325000745.1708610-4-chris.packham@alliedtelesis.co.nz>
On 25/03/2022 01:07, Chris Packham wrote:
> The armada-37xx SoC dtsi includes this as a compatible string. Add it to
> the dt-binding.
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
>
> Notes:
> Changes in v3:
> - new
>
> .../devicetree/bindings/mmc/marvell,xenon-sdhci.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.yaml b/Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.yaml
> index 326ac3fa36b5..776bed5046fa 100644
> --- a/Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.yaml
> +++ b/Documentation/devicetree/bindings/mmc/marvell,xenon-sdhci.yaml
> @@ -31,6 +31,10 @@ properties:
> - const: marvell,armada-ap807-sdhci
> - const: marvell,armada-ap806-sdhci
>
> + - items:
> + - const: marvell,armada-3700-sdhci
> + - const: marvell,sdhci-xenon
Do you know of any usages of marvell,armada-3700-sdhci alone (without
sdhci-xenon)? If not, it should be removed from the enum before (the one
added in your patch #2). It does not look correct to have it both as
standalone compatible and one compatible with sdhci-xenon. Either it is
compatible with sdhci-xenon or not. :)
I suggested before to make this change here as separate patch, but I
think I missed the fact that it is simple correction of
armada-3700-sdhci compatible. Such simple corrections can be done within
same patch as conversion, with explanation in commit msg (which was
missing in your v1).
To avoid unnecessary patch changes you could squash it with v1 and
include this in the commit msg (actually extend it to say that you are
correcting the 3700-sdhci compatible), or create patch #2 that way:
+ oneOf:
+ - enum:
+ - marvell,armada-cp110-sdhci
+ - marvell,armada-ap806-sdhci
+ - items:
+ - const: marvell,armada-ap807-sdhci
+ - const: marvell,armada-ap806-sdhci
+ - items:
+ - marvell,armada-3700-sdhci
so now you will only add xenon here. But then it is so small patch that
with explanation we usually include it in conversion.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-03-25 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 0:07 [PATCH v3 0/3] mmc: xenon: Convert to JSON schema Chris Packham
2022-03-25 0:07 ` [PATCH v3 1/3] arm64: dts: marvell: Update sdhci node names to match schema Chris Packham
2022-03-25 0:07 ` [PATCH v3 2/3] dt-bindings: mmc: xenon: Convert to JSON schema Chris Packham
2022-03-25 11:54 ` Krzysztof Kozlowski
2022-03-25 0:07 ` [PATCH v3 3/3] dt-bindings: mmc: xenon: add marvell,sdhci-xenon compatible Chris Packham
2022-03-25 12:04 ` Krzysztof Kozlowski [this message]
2022-03-28 23:41 ` Chris Packham
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=475d2af6-38cd-47a1-61b2-6b1298bf505d@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=huziji@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=ulf.hansson@linaro.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®