From: Brian Masney <bmasney@redhat.com>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Manivannan Sadhasivam <mani@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>,
Tejun Heo <tj@kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] regulator: core: Add option to prevent disabling unused regulators
Date: Mon, 30 Oct 2023 10:53:50 -0400 [thread overview]
Message-ID: <ZT/DfnWWYkYPzkWB@brian-x1> (raw)
In-Reply-To: <20231028102423.179400-1-javierm@redhat.com>
On Sat, Oct 28, 2023 at 12:24:03PM +0200, Javier Martinez Canillas wrote:
> This may be useful for debugging and develompent purposes, when there are
> drivers that depend on regulators to be enabled but do not request them.
>
> It is inspired from the clk_ignore_unused and pd_ignore_unused parameters,
> that are used to keep firmware-enabled clocks and power domains on even if
> these are not used by drivers.
>
> The parameter is not expected to be used in normal cases and should not be
> needed on a platform with proper driver support.
>
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
Thanks for posting this! I've had a need for this. With Randy's feedback
addressed:
Reviewed-by: Brian Masney <bmasney@redhat.com>
next prev parent reply other threads:[~2023-10-30 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 10:24 [PATCH] regulator: core: Add option to prevent disabling unused regulators Javier Martinez Canillas
2023-10-28 16:04 ` Randy Dunlap
2023-10-30 14:53 ` Brian Masney [this message]
2023-11-01 4:56 ` Manivannan Sadhasivam
2023-11-01 13:09 ` Mark Brown
2023-11-02 9:33 ` Javier Martinez Canillas
2023-11-13 19:40 ` Mark Brown
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=ZT/DfnWWYkYPzkWB@brian-x1 \
--to=bmasney@redhat.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=javierm@redhat.com \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=paulmck@kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.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