From: Lee Yongjun <jun85566@gmail.com>
To: ulf.hansson@linaro.org, robh@kernel.org
Cc: krzk+dt@kernel.org, conor+dt@kernel.org, rjui@broadcom.com,
sbranden@broadcom.com, bcm-kernel-feedback-list@broadcom.com,
nsaenz@kernel.org, linux-mmc@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Lee Yongjun <jun85566@gmail.com>
Subject: [PATCH] dt-bindings: mmc: brcm,iproc-sdhci: allow dma-coherent property
Date: Fri, 6 Mar 2026 08:47:03 +0900 [thread overview]
Message-ID: <20260305234703.38490-1-jun85566@gmail.com> (raw)
The Broadcom iProc SDHCI controller supports DMA, but its binding
schema does not allow the 'dma-coherent' property.
As a result, dtbs_check reports the following validation errors
on the Northstar2 SoC:
mmc@66420000 (brcm,sdhci-iproc-cygnus): Unevaluated properties
are not allowed ('dma-coherent' was unexpected)
mmc@66430000 (brcm,sdhci-iproc-cygnus): Unevaluated properties
are not allowed ('dma-coherent' was unexpected)
Allow the 'dma-coherent' property in the schema to fix the validation
errors and accurately reflect the hardware capability.
Signed-off-by: Lee Yongjun <jun85566@gmail.com>
---
Documentation/devicetree/bindings/mmc/brcm,iproc-sdhci.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/brcm,iproc-sdhci.yaml b/Documentation/devicetree/bindings/mmc/brcm,iproc-sdhci.yaml
index 2f63f2cdeb71..579e44843404 100644
--- a/Documentation/devicetree/bindings/mmc/brcm,iproc-sdhci.yaml
+++ b/Documentation/devicetree/bindings/mmc/brcm,iproc-sdhci.yaml
@@ -38,6 +38,8 @@ properties:
type: boolean
description: Specifies that controller should use auto CMD12
+ dma-coherent: true
+
required:
- compatible
- reg
--
2.34.1
next reply other threads:[~2026-03-05 23:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 23:47 Lee Yongjun [this message]
2026-03-06 0:03 ` [PATCH] dt-bindings: mmc: brcm,iproc-sdhci: allow dma-coherent property Ray Jui
2026-03-06 8:45 ` Krzysztof Kozlowski
2026-03-06 0:06 ` Florian Fainelli
2026-03-06 1:21 ` Rob Herring (Arm)
2026-03-06 8:42 ` Krzysztof Kozlowski
2026-03-06 8:43 ` Krzysztof Kozlowski
2026-03-06 11:06 ` Lee Yongjun
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=20260305234703.38490-1-jun85566@gmail.com \
--to=jun85566@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nsaenz@kernel.org \
--cc=rjui@broadcom.com \
--cc=robh@kernel.org \
--cc=sbranden@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.