| +-+ |
| | defer-reset(gpx3) | |
| +-+ |
+-+
Signed-off-by: Houcheng Lin
---
.../devicetree/bindings/reset/gpio-defer-reset.txt | 30
drivers/reset/Kconfig | 8 +
drivers/reset/Makefile
e is run before driver init-call, can not add reset
sending here if it depends on a specific device's initialization.
Also it provides a DT node that helps both HW/SW developer to use this
feature.
Best regards,
Houcheng Lin
--
To unsubscribe from this list: send the line "unsubscribe
er-reset";
> reset-gpios = <&gpx3 5 GPIO_ACTIVE_LOW>;
> duration = <0>;
These DT properties looks simpler and better: Use of GPIO_ACTIVE_HIGH
and GPIO_ACTIVE_LOW increase readability for HW/SW developer, use
of <0> to indicate holding the reset signal.
+-+ |
| | defer-reset(gpx3) | |
| +-+ |
+-----+
Signed-off-by: Houcheng Lin
---
.../devicetree/bindings/gpio/gpio-defer-reset.txt | 22 +++
drivers/power/reset/Kconfig| 8 +
drivers/power/reset/Makefile | 1 +
drivers/power/reset/gpio
reviews :) Here are fixed of version 2:
- change location to drivers/power/reset
- remove unused #include
- change to use GPIO descriptor interface and use customer.h
- free resources after issue reset. However, if a enclosing
chip is not probled, the correpsonding reset will not s
ter the reset is
> applied.
On some hardware board's resetting signal's timing sequence depends on
initialization of a device. Pull the reseting logic onto the device level fits
the original hardware and no need to modify the chip driver's source code.
However, this mech
+-+ |
| | defer-reset(gpx3) | |
| +-+ |
+-----+
Signed-off-by: Houcheng Lin
---
drivers/gpio/Kconfig| 8 ++
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-defer-reset.c | 179
3 files changed, 188 insertions(+)
c
