From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: Hu Ziji <huziji@marvell.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] dt-bindings: mmc: marvell,xenon-sdhci: Drop requiring 2 clocks
Date: Wed, 26 Mar 2025 09:14:57 +0100 [thread overview]
Message-ID: <20250326-light-shellfish-of-aptitude-2e64aa@krzk-bin> (raw)
In-Reply-To: <20250320-dt-marvell-mmc-v1-3-e51002ea0238@kernel.org>
On Thu, Mar 20, 2025 at 04:35:48PM -0500, Rob Herring (Arm) wrote:
> The "axi" clock is optional on at least the "marvell,armada-ap806-sdhci"
> variant. Not sure what's correct here, so just drop the constraint.
>
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> ---
> .../devicetree/bindings/mmc/marvell,xenon-sdhci.yaml | 20 --------------------
> 1 file changed, 20 deletions(-)
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-26 8:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 21:35 [PATCH 0/3] dt-bindings: mmc: marvell,xenon-sdhci: Fix several validation warnings Rob Herring (Arm)
2025-03-20 21:35 ` [PATCH 1/3] dt-bindings: mmc: marvell,xenon-sdhci: Allow "dma-coherent" and "iommus" Rob Herring (Arm)
2025-03-26 8:13 ` Krzysztof Kozlowski
2025-03-20 21:35 ` [PATCH 2/3] dt-bindings: mmc: marvell,xenon-sdhci: Add reference to sdhci-common.yaml Rob Herring (Arm)
2025-03-26 8:13 ` Krzysztof Kozlowski
2025-03-20 21:35 ` [PATCH 3/3] dt-bindings: mmc: marvell,xenon-sdhci: Drop requiring 2 clocks Rob Herring (Arm)
2025-03-26 8:14 ` Krzysztof Kozlowski [this message]
2025-04-07 16:04 ` [PATCH 0/3] dt-bindings: mmc: marvell,xenon-sdhci: Fix several validation warnings Ulf Hansson
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=20250326-light-shellfish-of-aptitude-2e64aa@krzk-bin \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=huziji@marvell.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.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