Hi all, Here are a few experimental WIP patches to make ti-sysc provide resets for the devices connected to the interconnect. I've only tested this with 8250_omap. I played with implementing all the resets automatically where available, but we could of course map just the reset used via devicetree. There are lots of resets, and not that many users. So likely using the devicetree to map only the used resets makes most sense from memory consumption point of view. However, the reset control framework changes may be desired though. For example, MFD child devices may not get the data via devicetree. Note that for ti-sysc driver, this series depends on an earlier pending clean-up series posted at [0]. Regards, Tony [0] https://lore.kernel.org/linux-omap/20240410064010.57142-1-tony@xxxxxxxxxxx/T/#md369ba556149a2662f2cd5413863d29f054b27b8 Tony Lindgren (4): reset: Fall back to lookup if no reset node is found reset: Allow removing a lookup bus: ti-sysc: Implement reset control framework for soft reset serial: 8250: omap: Use reset control for resets drivers/bus/ti-sysc.c | 109 ++++++++++++++++++++++++++++ drivers/reset/core.c | 36 ++++++++- drivers/tty/serial/8250/8250_omap.c | 66 ++++++----------- include/linux/reset-controller.h | 7 ++ 4 files changed, 174 insertions(+), 44 deletions(-) -- 2.44.0
