Linux Watchdog driver development
 help / color / mirror / Atom feed
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Wim Van Sebroeck <wim@linux-watchdog.org>,
	Guenter Roeck <linux@roeck-us.net>
Cc: Tero Kristo <t-kristo@kernel.org>,
	<linux-watchdog@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	<linux-arm-kernel@lists.infradead.org>, <afd@ti.com>,
	<n-francis@ti.com>
Subject: [PATCH 0/2] watchdog: rti_wdt: Disable module when unused
Date: Fri, 10 Nov 2023 15:37:24 +0530	[thread overview]
Message-ID: <20231110100726.2930218-1-vigneshr@ti.com> (raw)

This series adds couple of fixes to rti_wdt driver so that module is
disabled when unused. First patch is cleanup to use devm_* API and
second patch drops RPM count when unused.

On K3 SoCs, each RTI is paired to a CPU/GPU core. So disabling such
cores (CPU hotplug) would require corresponding RTIs to be off. This
series enables hotplug of the core, if the corresponding watchdog was
unused.


Vignesh Raghavendra (2):
  watchdog: rti_wdt: Use managed APIs to handle runtime PM
  watchdog: rti_wdt: Drop RPM watchdog when unused

 drivers/watchdog/rti_wdt.c | 39 +++++++++++++++++---------------------
 1 file changed, 17 insertions(+), 22 deletions(-)

-- 
2.42.0


             reply	other threads:[~2023-11-10 18:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10 10:07 Vignesh Raghavendra [this message]
2023-11-10 10:07 ` [PATCH 1/2] watchdog: rti_wdt: Use managed APIs to handle runtime PM Vignesh Raghavendra
2023-11-10 15:03   ` Guenter Roeck
2023-11-21  4:00     ` Vignesh Raghavendra
2023-11-10 10:07 ` [PATCH 2/2] watchdog: rti_wdt: Drop RPM watchdog when unused Vignesh Raghavendra
2023-11-10 15:05   ` Guenter Roeck

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=20231110100726.2930218-1-vigneshr@ti.com \
    --to=vigneshr@ti.com \
    --cc=afd@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=n-francis@ti.com \
    --cc=t-kristo@kernel.org \
    --cc=wim@linux-watchdog.org \
    /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