From: Rob Herring <robh@kernel.org>
To: Charan Pedumuru <charan.pedumuru@gmail.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Taichi Sugaya <sugaya.taichi@socionext.com>,
Takao Orito <orito.takao@socionext.com>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mmc: socionext,milbeaut-m10v-sdhci-3.0: convert to DT schema
Date: Mon, 27 Oct 2025 08:57:52 -0500 [thread overview]
Message-ID: <20251027135752.GA316916-robh@kernel.org> (raw)
In-Reply-To: <20251023-milbeaut-v1-1-3e4ff67110ad@gmail.com>
On Thu, Oct 23, 2025 at 05:37:36PM +0000, Charan Pedumuru wrote:
> Convert SOCIONEXT Milbeaut SDHCI controller binding to YAML format.
> Add a new property "voltage-ranges" to resolve dt_check errors.
>
> Signed-off-by: Charan Pedumuru <charan.pedumuru@gmail.com>
> ---
> .../devicetree/bindings/mmc/sdhci-milbeaut.txt | 30 ---------
> .../mmc/socionext,milbeaut-m10v-sdhci-3.0.yaml | 78 ++++++++++++++++++++++
> 2 files changed, 78 insertions(+), 30 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/mmc/sdhci-milbeaut.txt b/Documentation/devicetree/bindings/mmc/sdhci-milbeaut.txt
> deleted file mode 100644
> index 627ee89c125b..000000000000
> --- a/Documentation/devicetree/bindings/mmc/sdhci-milbeaut.txt
> +++ /dev/null
> @@ -1,30 +0,0 @@
> -* SOCIONEXT Milbeaut SDHCI controller
> -
> -This file documents differences between the core properties in mmc.txt
> -and the properties used by the sdhci_milbeaut driver.
> -
> -Required properties:
> -- compatible: "socionext,milbeaut-m10v-sdhci-3.0"
> -- clocks: Must contain an entry for each entry in clock-names. It is a
> - list of phandles and clock-specifier pairs.
> - See ../clocks/clock-bindings.txt for details.
> -- clock-names: Should contain the following two entries:
> - "iface" - clock used for sdhci interface
> - "core" - core clock for sdhci controller
> -
> -Optional properties:
> -- fujitsu,cmd-dat-delay-select: boolean property indicating that this host
> - requires the CMD_DAT_DELAY control to be enabled.
> -
> -Example:
> - sdhci3: mmc@1b010000 {
> - compatible = "socionext,milbeaut-m10v-sdhci-3.0";
> - reg = <0x1b010000 0x10000>;
> - interrupts = <0 265 0x4>;
> - voltage-ranges = <3300 3300>;
> - bus-width = <4>;
> - clocks = <&clk 7>, <&ahb_clk>;
> - clock-names = "core", "iface";
> - cap-sdio-irq;
> - fujitsu,cmd-dat-delay-select;
> - };
> diff --git a/Documentation/devicetree/bindings/mmc/socionext,milbeaut-m10v-sdhci-3.0.yaml b/Documentation/devicetree/bindings/mmc/socionext,milbeaut-m10v-sdhci-3.0.yaml
> new file mode 100644
> index 000000000000..6b67bef30347
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mmc/socionext,milbeaut-m10v-sdhci-3.0.yaml
> @@ -0,0 +1,78 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mmc/socionext,milbeaut-m10v-sdhci-3.0.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: SOCIONEXT Milbeaut SDHCI controller
> +
> +maintainers:
> + - Taichi Sugaya <sugaya.taichi@socionext.com>
> + - Takao Orito <orito.takao@socionext.com>
> +
> +description:
> + The SOCIONEXT Milbeaut SDHCI controller is a specialized SD Host
> + Controller found in some of Socionext's Milbeaut image processing SoCs.
> + It features a dedicated "bridge controller." This bridge controller
> + implements special functions like reset control, clock management for
> + various SDR modes (SDR12, SDR25, SDR50) and physical pin property settings.
> +
> +allOf:
> + - $ref: sdhci-common.yaml#
> +
> +properties:
> + compatible:
> + const: socionext,milbeaut-m10v-sdhci-3.0
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 2
> +
> + clock-names:
> + items:
> + - const: core
> + - const: iface
> +
> + fujitsu,cmd-dat-delay-select:
> + description:
> + Its presence indicates that the controller requires a specific command
> + and data line delay selection mechanism for proper operation, particularly
> + when dealing with high-speed SD/eMMC modes.
> + type: boolean
> +
> + voltage-ranges:
> + $ref: /schemas/types.yaml#/definitions/uint32-matrix
Sounds more like a uint32-array.
> + description:
> + Two cells are required, first cell specifies minimum slot voltage (mV),
> + second cell specifies maximum slot voltage (mV).
> + maxItems: 1
You can better describe it like this:
items:
- description: minimum slot voltage (mV)
- description: maximum slot voltage (mV)
next prev parent reply other threads:[~2025-10-27 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 17:37 [PATCH] dt-bindings: mmc: socionext,milbeaut-m10v-sdhci-3.0: convert to DT schema Charan Pedumuru
2025-10-27 13:57 ` Rob Herring [this message]
2025-10-27 14:11 ` Charan Pedumuru
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=20251027135752.GA316916-robh@kernel.org \
--to=robh@kernel.org \
--cc=charan.pedumuru@gmail.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=orito.takao@socionext.com \
--cc=sugaya.taichi@socionext.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.