Linux-Serial Archive mirror
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <20240411052257.2113-1-tony@atomide.com> (raw)

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

             reply	other threads:[~2024-04-11  5:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11  5:22 Tony Lindgren [this message]
2024-04-11  5:22 ` [RFC PATCH 1/4] reset: Fall back to lookup if no reset node is found Tony Lindgren
2024-04-11  5:22 ` [RFC PATCH 2/4] reset: Allow removing a lookup Tony Lindgren
2024-04-11  5:22 ` [RFC PATCH 3/4] bus: ti-sysc: Implement reset control framework for soft reset Tony Lindgren
2024-04-11  5:22 ` [RFC PATCH 4/4] serial: 8250: omap: Use reset control for resets Tony Lindgren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240411052257.2113-1-tony@atomide.com \
    --to=tony@atomide.com \
    --cc=d-gole@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).