Hi all, this is my third attempt to fix the ssd1307fb OLED driver reset. In the second attempt [1] Rob suggested to take different aproach. That is to apply what was originaly part of the first round and eventually merged but reverted later on [2][3]. Next step is to apply a fixup for the single user (in-tree) that uses this OLED. As Rob suggested, the fixup may be applied only after someone complains their display broke. I am not really sure what is the propper way to handle this so the series contains the original patches + a minor fix in the docs and the fixup as the last patch. Adding Alexandre and Maxime from Bootlin to the Cc list as you seem to be the last ones who touched the Crystalfontz platform. Your coment regarding the status of the platform and whether the fixup should be applied straight away or not at all will be appreciated. Thank you, Michal [1] https://patchwork.kernel.org/patch/10665597/#22327227 [2] https://patchwork.kernel.org/patch/10617729/ [3] https://patchwork.kernel.org/patch/10617731/#22257175 Michal Vokáč (4): dt-bindings: display: ssd1307fb: Remove reset-active-low from examples video: ssd1307fb: Do not hard code active-low reset sequence ARM: dts: imx28-cfa10036: Fix the reset gpio signal polarity ARM: mxs: cfa10036: Fixup OLED display reset polarity .../devicetree/bindings/display/ssd1307fb.txt | 2 - arch/arm/boot/dts/imx28-cfa10036.dts | 3 +- arch/arm/mach-mxs/mach-mxs.c | 45 ++++++++++++++++++++++ drivers/video/fbdev/ssd1307fb.c | 4 +- 4 files changed, 49 insertions(+), 5 deletions(-) -- 2.1.4
