From: Benjamin Bara <bbara93@gmail.com>
To: broonie@kernel.org
Cc: DLG-Adam.Ward.opensource@dm.renesas.com, bbara93@gmail.com,
benjamin.bara@skidata.com, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, mazziesaccount@gmail.com,
support.opensource@diasemi.com
Subject: Re: [PATCH RFC 1/2] regulator: introduce regulator monitoring constraints
Date: Thu, 20 Apr 2023 16:54:50 +0200 [thread overview]
Message-ID: <20230420145450.1033819-1-bbara93@gmail.com> (raw)
In-Reply-To: <90c4c45b-daae-4f38-a60c-6bb8d33c025d@sirena.org.uk>
On Thu, 20 Apr 2023 at 16:37, Mark Brown <broonie@kernel.org> wrote:
> Right, but in any case where the monitoring is enabled then these
> properties would also be needed so there's no point in separately
> configuring it.
> The driver can supply flags to tell the core to do things like it
> already does for a whole range of other things, there's no need to
> force things to be configured per system in order to factor things
> out. It's just a question of where the core gets information from.
Ah, got it. Thanks for clarification.
next prev parent reply other threads:[~2023-04-20 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 10:29 [PATCH RFC 0/2] regulator: dynamic voltage monitoring support Benjamin Bara
2023-04-20 10:29 ` [PATCH RFC 1/2] regulator: introduce regulator monitoring constraints Benjamin Bara
2023-04-20 11:33 ` Matti Vaittinen
2023-04-20 14:29 ` Benjamin Bara
2023-04-20 14:50 ` Mark Brown
2023-04-20 12:17 ` Mark Brown
2023-04-20 14:30 ` Benjamin Bara
2023-04-20 14:37 ` Mark Brown
2023-04-20 14:54 ` Benjamin Bara [this message]
2023-04-20 10:29 ` [PATCH RFC 2/2] regulator: da9063: disable monitoring while regulator is off Benjamin Bara
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=20230420145450.1033819-1-bbara93@gmail.com \
--to=bbara93@gmail.com \
--cc=DLG-Adam.Ward.opensource@dm.renesas.com \
--cc=benjamin.bara@skidata.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=support.opensource@diasemi.com \
/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