aboutsummaryrefslogtreecommitdiff
path: root/Bindings/mmc/mmc-controller.yaml
diff options
context:
space:
mode:
authorEmmanuel Vadot <manu@FreeBSD.org>2020-04-14 16:56:11 +0000
committerEmmanuel Vadot <manu@FreeBSD.org>2020-04-14 16:56:11 +0000
commit937eaf8bbdcf7e2cd3231b71940f9221e6857210 (patch)
treef35da0d4b9188f1cb082442854ce86fcca10b7b4 /Bindings/mmc/mmc-controller.yaml
parent995ee34fd27211af598f9adf111cb49609d1b3de (diff)
Notes
Diffstat (limited to 'Bindings/mmc/mmc-controller.yaml')
-rw-r--r--Bindings/mmc/mmc-controller.yaml6
1 files changed, 3 insertions, 3 deletions
diff --git a/Bindings/mmc/mmc-controller.yaml b/Bindings/mmc/mmc-controller.yaml
index b130450c3b342..8fded83c519ad 100644
--- a/Bindings/mmc/mmc-controller.yaml
+++ b/Bindings/mmc/mmc-controller.yaml
@@ -96,11 +96,10 @@ properties:
description:
When set, no physical write-protect line is present. This
property should only be specified when the controller has a
- dedicated write-protect detection logic. If a GPIO is always
- used for the write-protect detection. If a GPIO is always used
+ dedicated write-protect detection logic. If a GPIO is always used
for the write-protect detection logic, it is sufficient to not
specify the wp-gpios property in the absence of a write-protect
- line.
+ line. Not used in combination with eMMC or SDIO.
wp-gpios:
description:
@@ -371,6 +370,7 @@ examples:
mmc3: mmc@1c12000 {
#address-cells = <1>;
#size-cells = <0>;
+ reg = <0x1c12000 0x200>;
pinctrl-names = "default";
pinctrl-0 = <&mmc3_pins_a>;
vmmc-supply = <&reg_vmmc3>;