Re: [PATCH v2 2/3] mmc: sh_mobile_sdhi: explain clock bindings
From: Wolfram Sang <hidden>
Date: 2017-01-17 20:33:40
Also in:
linux-mmc, linux-renesas-soc
On Tue, Jan 17, 2017 at 02:59:39PM -0500, Chris Brandt wrote:
quoted hunk ↗ jump to hunk
In the case of a single clock source, you don't need names. However, if the controller has 2 clock sources, you need to name them correctly so the driver can find the 2nd one. Signed-off-by: Chris Brandt <chris.brandt@renesas.com> --- Documentation/devicetree/bindings/mmc/tmio_mmc.txt | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+)diff --git a/Documentation/devicetree/bindings/mmc/tmio_mmc.txt b/Documentation/devicetree/bindings/mmc/tmio_mmc.txt index a1650ed..258b98c 100644 --- a/Documentation/devicetree/bindings/mmc/tmio_mmc.txt +++ b/Documentation/devicetree/bindings/mmc/tmio_mmc.txt@@ -25,8 +25,29 @@ Required properties: "renesas,sdhi-r8a7795" - SDHI IP on R8A7795 SoC "renesas,sdhi-r8a7796" - SDHI IP on R8A7796 SoC +- clocks: Most controllers only have 1 clock source per cahnnel. However, some
channel.
+ have 2. If 2 clocks are specified, you must name them as "core" and
Maybe "However, some have a second clock dedicated to card detection."?