linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Lin <shawn.lin@rock-chips.com>
To: Jun Nie <jun.nie@linaro.org>,
	shawn.guo@linaro.org, xie.baoyou@zte.com.cn
Cc: shawn.lin@rock-chips.com, ulf.hansson@linaro.org,
	jh80.chung@samsung.com, jason.liu@linaro.org,
	linux-mmc@vger.kernel.org
Subject: Re: [PATCH v5 1/5] mmc: dt-bindings: add ZTE ZX296718 MMC bindings
Date: Mon, 14 Nov 2016 15:58:51 +0800	[thread overview]
Message-ID: <b72dcd9c-aa90-a487-dbfb-6682fcdf015b@rock-chips.com> (raw)
In-Reply-To: <1478568298-18380-2-git-send-email-jun.nie@linaro.org>

On 2016/11/8 9:24, Jun Nie wrote:
> Document the device-tree binding of ZTE MMC host on
> ZX296718 SoC.
>
> Signed-off-by: Jun Nie <jun.nie@linaro.org>
> ---
>  .../devicetree/bindings/mmc/zx-dw-mshc.txt         | 35 ++++++++++++++++++++++
>  1 file changed, 35 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/mmc/zx-dw-mshc.txt
>
> diff --git a/Documentation/devicetree/bindings/mmc/zx-dw-mshc.txt b/Documentation/devicetree/bindings/mmc/zx-dw-mshc.txt
> new file mode 100644
> index 0000000..c175c4b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mmc/zx-dw-mshc.txt
> @@ -0,0 +1,35 @@
> +* ZTE specific extensions to the Synopsys Designware Mobile Storage
> +  Host Controller
> +
> +The Synopsys designware mobile storage host controller is used to interface
> +a SoC with storage medium such as eMMC or SD/MMC cards. This file documents
> +differences between the core Synopsys dw mshc controller properties described
> +by synopsys-dw-mshc.txt and the properties used by the ZTE specific
> +extensions to the Synopsys Designware Mobile Storage Host Controller.
> +
> +Required Properties:
> +
> +* compatible: should be
> +	- "zte,zx296718-dw-mshc": for ZX SoCs
> +
> +Example:
> +
> +	mmc1: mmc@1110000 {
> +		compatible = "zte,zx296718-dw-mshc";
> +		#address-cells = <1>;
> +		#size-cells = <0>;
> +		reg = <0x01110000 0x1000>;
> +		interrupts = <GIC_SPI 15 IRQ_TYPE_LEVEL_HIGH>;
> +		fifo-depth = <32>;
> +		data-addr = <0x200>;
> +		fifo-watermark-aligned;
> +		bus-width = <4>;
> +		clock-frequency = <50000000>;

do you need both clock-frequency and max-frequency here?

> +		clocks = <&topcrm SD0_AHB>, <&topcrm SD0_WCLK>;
> +		clock-names = "biu", "ciu";
> +		num-slots = <1>;
> +		max-frequency = <50000000>;
> +		cap-sdio-irq;
> +		cap-sd-highspeed;
> +		status = "disabled";
> +	};
>


-- 
Best Regards
Shawn Lin


  reply	other threads:[~2016-11-14  7:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20161108012533epcas5p19f44057ff5477f35ebf057527fea9788@epcas5p1.samsung.com>
2016-11-08  1:24 ` [PATCH v5 0/5] Add intial support to DW MMC host on ZTE SoC Jun Nie
2016-11-08  1:24   ` [PATCH v5 1/5] mmc: dt-bindings: add ZTE ZX296718 MMC bindings Jun Nie
2016-11-14  7:58     ` Shawn Lin [this message]
2016-11-14 10:00       ` Jun Nie
2016-11-14 10:04         ` Jaehoon Chung
2016-11-15  0:48           ` Shawn Lin
2016-11-15  5:21             ` Jaehoon Chung
2016-11-15  7:49               ` Shawn Lin
2016-11-16  1:54                 ` Jaehoon Chung
2016-11-08  1:24   ` [PATCH v5 2/5] mmc: zx: Initial support for ZX mmc controller Jun Nie
2016-11-14  8:07     ` Shawn Lin
2016-11-14  8:50       ` Jun Nie
2016-11-14  9:03         ` Shawn Lin
2016-11-14 10:02           ` Jun Nie
2016-11-08  1:24   ` [PATCH v5 3/5] Documentation: synopsys-dw-mshc: add binding for fifo quirks Jun Nie
2016-11-08  1:24   ` [PATCH v5 4/5] mmc: dw: Add fifo address property Jun Nie
2016-11-14  8:12     ` Shawn Lin
2016-11-08  1:24   ` [PATCH v5 5/5] mmc: dw: Add fifo watermark alignment property Jun Nie
2016-11-14  8:10     ` Shawn Lin
2016-11-14  3:21   ` [PATCH v5 0/5] Add intial support to DW MMC host on ZTE SoC Jun Nie
2016-11-14  3:39     ` Jaehoon Chung
2016-11-18  2:16   ` Jaehoon Chung
2016-11-18  6:34     ` Jun Nie

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=b72dcd9c-aa90-a487-dbfb-6682fcdf015b@rock-chips.com \
    --to=shawn.lin@rock-chips.com \
    --cc=jason.liu@linaro.org \
    --cc=jh80.chung@samsung.com \
    --cc=jun.nie@linaro.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=shawn.guo@linaro.org \
    --cc=ulf.hansson@linaro.org \
    --cc=xie.baoyou@zte.com.cn \
    /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;
as well as URLs for NNTP newsgroup(s).