public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: "ping.gao" <ping.gao@samsung.com>
To: ulf.hansson@linaro.org, jh80.chung@samsung.com
Cc: shawn.lin@rock-chips.com, krzk@kernel.org, krzk+dt@kernel.org,
	robh@kernel.org, conor+dt@kernel.org, linux-mmc@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	kwangwon.min@samsung.com, hy50.seo@samsung.com,
	Ping Gao <ping.gao@samsung.com>
Subject: [PATCH v4 1/3] dt-bindings: mmc: synopsys-dw-mshc: relax clocks constraint
Date: Sat, 28 Feb 2026 14:24:55 +0800	[thread overview]
Message-ID: <20260228062457.3210099-2-ping.gao@samsung.com> (raw)
In-Reply-To: <20260228062457.3210099-1-ping.gao@samsung.com>

From: Ping Gao <ping.gao@samsung.com>

In some SoC designs (e.g., certain Samsung Exynos platforms), the Bus
Interface Unit (BIU) and Card Interface Unit (CIU) clocks are tied
together or driven by a single clock source. In such hardware
configurations, only one clock entry needs to be described in the
device tree.

Relax the clocks and clock-names constraints to allow a single clock
while maintaining backward compatibility for existing dual-clock
designs.

Signed-off-by: Ping Gao <ping.gao@samsung.com>
---
 .../devicetree/bindings/mmc/synopsys-dw-mshc.yaml   | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.yaml b/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.yaml
index a6292777e376..47dff8d4be27 100644
--- a/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.yaml
+++ b/Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.yaml
@@ -24,16 +24,21 @@ properties:
     maxItems: 1
 
   clocks:
-    minItems: 2
+    minItems: 1
     maxItems: 2
     description:
       Handle to "biu" and "ciu" clocks for the
       bus interface unit clock and the card interface unit clock.
 
   clock-names:
-    items:
-      - const: biu
-      - const: ciu
+    minItems: 1
+    maxItems: 2
+    oneOf:
+      - items:
+          - const: biu
+          - const: ciu
+      - items:
+          - const: ciu
 
   iommus:
     maxItems: 1
-- 
2.50.1


  reply	other threads:[~2026-02-28  6:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20260228062020epcas5p1e498c4fc67f590f4243645288c492f01@epcas5p1.samsung.com>
2026-02-28  6:24 ` [PATCH v4 0/3] mmc: dw_mmc: Support optional BIU clock ping.gao
2026-02-28  6:24   ` ping.gao [this message]
2026-02-28  9:44     ` [PATCH v4 1/3] dt-bindings: mmc: synopsys-dw-mshc: relax clocks constraint Krzysztof Kozlowski
2026-02-28 10:12       ` Krzysztof Kozlowski
2026-03-06  2:05         ` ping.gao
2026-02-28  6:24   ` [PATCH v4 2/3] mmc: dw_mmc-k3: before set biu_clk rate, check biu_clk available or not ping.gao
2026-02-28  6:24   ` [PATCH v4 3/3] mmc: dw_mmc: Using devm_clk_get_optional() for biu_clk ping.gao
2026-02-28  9:44     ` 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=20260228062457.3210099-2-ping.gao@samsung.com \
    --to=ping.gao@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hy50.seo@samsung.com \
    --cc=jh80.chung@samsung.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kwangwon.min@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=shawn.lin@rock-chips.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