From: Tuomas Tynkkynen Date: Sat, 23 Dec 2017 00:34:12 +0000 (+0200) Subject: mmc: Don't reference Linux-specific OF_GPIO_ACTIVE_LOW flag in DT binding X-Git-Tag: v4.19~1687^2~13 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=d7e9ab3c6d76c6480d6b40525375995c0d8526fc;p=platform%2Fkernel%2Flinux-rpi.git mmc: Don't reference Linux-specific OF_GPIO_ACTIVE_LOW flag in DT binding OF_GPIO_ACTIVE_LOW is a Linux implementation detail. The binding document should be referring to GPIO_ACTIVE_LOW found in include/dt-bindings/gpio/gpio.h. Signed-off-by: Tuomas Tynkkynen Signed-off-by: Rob Herring --- diff --git a/Documentation/devicetree/bindings/mmc/mmc.txt b/Documentation/devicetree/bindings/mmc/mmc.txt index fb11ae8..467cd7b 100644 --- a/Documentation/devicetree/bindings/mmc/mmc.txt +++ b/Documentation/devicetree/bindings/mmc/mmc.txt @@ -67,10 +67,10 @@ logic applies to the "wp-inverted" property. CD and WP lines can be implemented on the hardware in one of two ways: as GPIOs, specified in cd-gpios and wp-gpios properties, or as dedicated pins. Polarity of dedicated pins can be specified, using *-inverted properties. GPIO polarity can -also be specified using the OF_GPIO_ACTIVE_LOW flag. This creates an ambiguity +also be specified using the GPIO_ACTIVE_LOW flag. This creates an ambiguity in the latter case. We choose to use the XOR logic for GPIO CD and WP lines. This means, the two properties are "superimposed," for example leaving the -OF_GPIO_ACTIVE_LOW flag clear and specifying the respective *-inverted +GPIO_ACTIVE_LOW flag clear and specifying the respective *-inverted property property results in a double-inversion and actually means the "normal" line polarity is in effect.