blob: 332dab5b66675af0632d73478ea5101165404a39 [file] [log] [blame]
From 84e03feab423e6bde5568c8dcd35b7217ceec4a6 Mon Sep 17 00:00:00 2001
From: Chris Brandt <>
Date: Wed, 25 Jan 2017 15:28:09 -0500
Subject: [PATCH 159/255] mmc: sh_mobile_sdhi: explain clock bindings
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. The 2nd clock is for the internal
card detect logic.
Signed-off-by: Chris Brandt <>
Reviewed-by: Geert Uytterhoeven <>
Signed-off-by: Ulf Hansson <>
Reviewed-by: Wolfram Sang <>
Acked-by: Rob Herring <>
(cherry picked from commit 62a4cdead56e5715c61aadd41ab66f49bd3170f1)
Signed-off-by: Simon Horman <>
Documentation/devicetree/bindings/mmc/tmio_mmc.txt | 13 +++++++++++++
1 file changed, 13 insertions(+)
--- a/Documentation/devicetree/bindings/mmc/tmio_mmc.txt
+++ b/Documentation/devicetree/bindings/mmc/tmio_mmc.txt
@@ -25,6 +25,19 @@ 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 channel. However, on
+ some variations of this controller, the internal card detection
+ logic that exists in this controller is sectioned off to be run by a
+ separate second clock source to allow the main core clock to be turned
+ off to save power.
+ If 2 clocks are specified by the hardware, you must name them as
+ "core" and "cd". If the controller only has 1 clock, naming is not
+ required.
+ Below is the number clocks for each supported SoC:
+ 1: SH73A0, R8A73A4, R8A7740, R8A7778, R8A7779, R8A7790
+ R8A7791, R8A7792, R8A7793, R8A7794, R8A7795, R8A7796
+ 2: R7S72100
Optional properties:
- toshiba,mmc-wrprotect-disable: write-protect detection is unavailable
- pinctrl-names: should be "default", "state_uhs"