From: Heiko Stuebner <heiko@sntech.de>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org,
Kever Yang <kever.yang@rock-chips.com>,
devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Jisheng Zhang <jszhang@kernel.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH v2 02/17] dt-bindings: mmc: Add support for rk3562 eMMC
Date: Thu, 26 Dec 2024 01:35:29 +0100 [thread overview]
Message-ID: <5169773.31r3eYUQgx@phil> (raw)
In-Reply-To: <20241224094920.3821861-3-kever.yang@rock-chips.com>
Hi Kever,
Am Dienstag, 24. Dezember 2024, 10:49:05 CET schrieb Kever Yang:
> rk3562 is using the same controller as rk3588.
>
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> ---
>
> Changes in v2: None
>
> .../devicetree/bindings/mmc/snps,dwcmshc-sdhci.yaml | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/mmc/snps,dwcmshc-sdhci.yaml b/Documentation/devicetree/bindings/mmc/snps,dwcmshc-sdhci.yaml
> index c3d5e0230af1..33f4288ff879 100644
> --- a/Documentation/devicetree/bindings/mmc/snps,dwcmshc-sdhci.yaml
> +++ b/Documentation/devicetree/bindings/mmc/snps,dwcmshc-sdhci.yaml
> @@ -14,16 +14,19 @@ properties:
> compatible:
> oneOf:
oneOf means what the naming suggests, the compatible needs to
either follow the "items", the old one means:
"rockchip,rk3576-dwcmshc", "rockchip,rk3588-dwcmshc"
or the enum below, which means "one" element from the enum
list.
> - items:
> - - const: rockchip,rk3576-dwcmshc
> + - const: rockchip,rk3568-dwcmshc
> - const: rockchip,rk3588-dwcmshc
That means, both the rk3568 and rk3588 entries in the enum below need
to stay, as they represent the single-value compatibles and the items
above should definitly not mention the rk3568, but instead be modified
to just include the rk3562. So just modify the items above to include it:
- items:
- enum:
- rockchip,rk3562-dwcmshc
- rockchip,rk3576-dwcmshc
- const: rockchip,rk3588-dwcmshc
> - enum:
> - - rockchip,rk3568-dwcmshc
> - - rockchip,rk3588-dwcmshc
> - snps,dwcmshc-sdhci
> - sophgo,cv1800b-dwcmshc
> - sophgo,sg2002-dwcmshc
> - sophgo,sg2042-dwcmshc
> - thead,th1520-dwcmshc
Heiko
next prev parent reply other threads:[~2024-12-26 0:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 9:49 [PATCH v2 00/17] rockchip: Add rk3562 support Kever Yang
2024-12-24 9:49 ` [PATCH v2 02/17] dt-bindings: mmc: Add support for rk3562 eMMC Kever Yang
2024-12-24 13:53 ` Rob Herring (Arm)
2024-12-26 0:35 ` Heiko Stuebner [this message]
2024-12-24 9:49 ` [PATCH v2 03/17] dt-bindings: mmc: rockchip-dw-mshc: Add rk3562 compatible string Kever Yang
2024-12-26 0:39 ` Heiko Stuebner
2025-01-10 8:00 ` Kever Yang
2024-12-27 7:41 ` Krzysztof Kozlowski
2024-12-27 7:38 ` [PATCH v2 00/17] rockchip: Add rk3562 support Krzysztof Kozlowski
2025-01-10 7:58 ` Kever Yang
2024-12-27 8:32 ` Krzysztof Kozlowski
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=5169773.31r3eYUQgx@phil \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jszhang@kernel.org \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--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