Received-SPF: pass (google.com: domain of linux-kernel+bounces-139776-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Cc: Dhruva Gole <d-gole@ti.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org
Subject: [RFC PATCH 0/4] Provide interconnect resets for ti-sysc users
Date: Thu, 11 Apr 2024 08:22:53 +0300
Message-ID: <20240411052257.2113-1-tony@atomide.com>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

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@atomide.com/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