This reverts commit 519b4dba586198eed8f72ba07bc71808af2e0e32.
It is true that the actual implementation has never been there. But
contrary to what the reverted commit message says it does make sense
to add it.
Current implementation of the reset signal is hard-coded to active low
with the assumption that reset-gpios is specified as GPIO_ACTIVE_HIGH.
That is technically wrong as the DTS authors should know that SSD130x
displays need active low reset and hence they are temped to use
GPIO_ACTIVE_LOW. But with that the reset is broken. So reset-acive-low
property can be used to invert the signal once again to fix this.
Signed-off-by: Michal Vokáč <michal.vokac@xxxxxxxxx>
---
Documentation/devicetree/bindings/display/ssd1307fb.txt | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/display/ssd1307fb.txt b/Documentation/devicetree/bindings/display/ssd1307fb.txt
index 209d931..a5ead10 100644
--- a/Documentation/devicetree/bindings/display/ssd1307fb.txt
+++ b/Documentation/devicetree/bindings/display/ssd1307fb.txt
@@ -16,6 +16,8 @@ Required properties:
Optional properties:
- reset-gpios: The GPIO used to reset the OLED display, if available. See
Documentation/devicetree/bindings/gpio/gpio.txt for details.
+ - reset-active-low: Bool flag to indicate the GPIO specified in "reset-gpios"
+ property is active low.
- vbat-supply: The supply for VBAT
- solomon,segment-no-remap: Display needs normal (non-inverted) data column
to segment mapping
@@ -35,7 +37,7 @@ ssd1307: oled@3c {
compatible = "solomon,ssd1307fb-i2c";
reg = <0x3c>;
pwms = <&pwm 4 3000>;
- reset-gpios = <&gpio2 7>;
+ reset-gpios = <&gpio2 7 GPIO_ACTIVE_LOW>;
reset-active-low;
};
@@ -43,7 +45,7 @@ ssd1306: oled@3c {
compatible = "solomon,ssd1306fb-i2c";
reg = <0x3c>;
pwms = <&pwm 4 3000>;
- reset-gpios = <&gpio2 7>;
+ reset-gpios = <&gpio2 7 GPIO_ACTIVE_LOW>;
reset-active-low;
solomon,com-lrremap;
solomon,com-invdir;
--
2.1.4
