From: Rob Herring <robh@kernel.org>
To: Takao Orito <orito.takao@socionext.com>
Cc: ulf.hansson@linaro.org, mark.rutland@arm.com,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, masami.hiramatsu@linaro.org,
jaswinder.singh@linaro.org, sugaya.taichi@socionext.com,
kasai.kazuhiro@socionext.com, kanematsu.shinji@socionext.com
Subject: Re: [PATCH 1/2] dt-bindings: mmc: add DT bindings for Milbeaut SD controller
Date: Wed, 1 May 2019 19:44:22 -0500 [thread overview]
Message-ID: <20190502004422.GA2242@bogus> (raw)
In-Reply-To: <1556244392-15822-1-git-send-email-orito.takao@socionext.com>
On Fri, Apr 26, 2019 at 11:06:32AM +0900, Takao Orito wrote:
Needs a commit msg.
> Signed-off-by: Takao Orito <orito.takao@socionext.com>
> ---
> .../devicetree/bindings/mmc/sdhci-milbeaut.txt | 35 ++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mmc/sdhci-milbeaut.txt
>
> diff --git a/Documentation/devicetree/bindings/mmc/sdhci-milbeaut.txt b/Documentation/devicetree/bindings/mmc/sdhci-milbeaut.txt
> new file mode 100644
> index 0000000..7008462
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mmc/sdhci-milbeaut.txt
> @@ -0,0 +1,35 @@
> +* SOCIONEXT 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:
> +- vqmmc-supply: phandle to the regulator device tree node, mentioned
> + as the VCCQ/VDD_IO supply in the eMMC/SD specs.
> +- fujitsu,cmd-dat-delay-select: boolean property indicating that this host
> + requires the CMD_DAT_DELAY control to be enabled.
> +- sni,mmc-power-gpio: set property indicating that power on or off needs
> + control of gpios.
> +
> +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;
> + sni,mmc-power-gpio = <&pinctrl 53 GPIO_ACTIVE_HIGH>;
> + fujitsu,cmd-dat-delay-select;
Whitespace problem.
> + };
> --
> 1.9.1
>
>
next prev parent reply other threads:[~2019-05-02 0:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 2:06 [PATCH 1/2] dt-bindings: mmc: add DT bindings for Milbeaut SD controller Takao Orito
2019-04-29 10:24 ` Ulf Hansson
2019-05-07 9:14 ` orito.takao
2019-05-07 9:14 ` orito.takao
2019-05-02 0:44 ` Rob Herring [this message]
2019-05-07 9:20 ` orito.takao
2019-05-07 9:20 ` orito.takao
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=20190502004422.GA2242@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jaswinder.singh@linaro.org \
--cc=kanematsu.shinji@socionext.com \
--cc=kasai.kazuhiro@socionext.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masami.hiramatsu@linaro.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.