From: Mark Brown <broonie@kernel.org>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Naresh Solanki <naresh.solanki@9elements.com>,
zev@bewilderbeest.net, Sebastian Reichel <sre@kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v1 3/3] regulator: fixed: forward under-voltage events
Date: Thu, 12 Oct 2023 12:13:57 +0100 [thread overview]
Message-ID: <77de152a-c637-40a2-846f-e79f52ddbee1@sirena.org.uk> (raw)
In-Reply-To: <ZSebeJKa0sEzNzP4@dc78bmyyyyyyyyyyyyydt-3.rev.dnainternet.fi>
[-- Attachment #1: Type: text/plain, Size: 294 bytes --]
On Thu, Oct 12, 2023 at 10:08:40AM +0300, Matti Vaittinen wrote:
> In my eyes the device-tree is correct place for this information
> because whether an "anomaly" in regulator output compromises the system
> is a property of hardware.
Yes, it's mainly the handling that has a policy element.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-10-12 11:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231010085906.3440452-1-o.rempel@pengutronix.de>
[not found] ` <20231010085906.3440452-3-o.rempel@pengutronix.de>
[not found] ` <5e51792a-cc93-4364-a51b-c2b116d89369@sirena.org.uk>
[not found] ` <20231010125531.GA3268051@pengutronix.de>
2023-10-10 17:19 ` [PATCH v1 3/3] regulator: fixed: forward under-voltage events Mark Brown
2023-10-11 7:59 ` Oleksij Rempel
2023-10-11 11:38 ` Mark Brown
2023-10-12 7:08 ` Matti Vaittinen
2023-10-12 11:13 ` Mark Brown [this message]
2023-10-21 0:26 ` Sebastian Reichel
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=77de152a-c637-40a2-846f-e79f52ddbee1@sirena.org.uk \
--to=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=naresh.solanki@9elements.com \
--cc=o.rempel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sre@kernel.org \
--cc=zev@bewilderbeest.net \
/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