Hello everyone, thanks for the feedback I've received. This is the reworked RFC for adressing a platform specific ramp-up/ramp-down delay on GPIO outputs. Now the delays are neither specified as gpio-controller nor consumer-specific properties. v2 is a different approach than v1 in that it adds a new driver which will simply forward setting the GPIO output of specified GPIOs in OF node. The ramp-up/ramp-down delay can now be actually defined on consumer side, see Patch 1 or 3 for examples. Thanks a lot to the existing gpio-latch driver where I could learn/copy from a lot for creating this driver! Patch 1 is the new binding. I welcome improvements for the description, if needed. Patch 2 is the new driver. I'm open for a better name, if the current one is too ambiguous. Patch 3 is what I am actually using for testing. It is actually based on a not-yet-commited patch, but the diff should be enough for demonstration. Alexander Stein (3): dt-bindings: gpio: Add gpio-delay binding document gpio: Add gpio delay driver [DNI] arm64: dts: mba8mx: Use gpio-delay for LVDS bridge .../devicetree/bindings/gpio/gpio-delay.yaml | 75 ++++++++ arch/arm64/boot/dts/freescale/mba8mx.dtsi | 14 +- drivers/gpio/Kconfig | 8 + drivers/gpio/Makefile | 1 + drivers/gpio/gpio-delay.c | 164 ++++++++++++++++++ 5 files changed, 261 insertions(+), 1 deletion(-) create mode 100644 Documentation/devicetree/bindings/gpio/gpio-delay.yaml create mode 100644 drivers/gpio/gpio-delay.c -- 2.34.1
