public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Rob Herring <robh+dt@kernel.org>,
	kernel@pengutronix.de,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
	linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH v4 4/5] regulator: dt-bindings: Add 'regulator-uv-less-critical-window-ms' property
Date: Fri, 27 Oct 2023 16:26:18 -0500	[thread overview]
Message-ID: <169844197767.3399644.2264278989526622921.robh@kernel.org> (raw)
In-Reply-To: <20231026144824.4065145-5-o.rempel@pengutronix.de>


On Thu, 26 Oct 2023 16:48:23 +0200, Oleksij Rempel wrote:
> Introduces a new devicetree property to specifies the time window (in
> milliseconds) following a critical under-voltage (UV) event during which
> less critical actions can be safely carried out by the system.
> 
> Less Critical Actions:
> - Logging the under-voltage event for later analysis.
> - Saving less critical data that may be useful for diagnosing issues or
>   for audit purposes.
> 
> More Critical Actions (post the less critical window):
> - Initiating procedures to properly shutdown hardware to prevent damage.
> 
> The 'regulator-uv-less-critical-window-ms' property is crucial for
> conveying board-specific hardware characteristics, not for enforcing a
> certain policy. The time window represented by this property is derived
> from the physical attributes of the hardware like the capacity of
> on-board capacitors, the power consumption of the components, and the
> time needed to safely shut down hardware to prevent damage. These
> attributes can significantly vary between different boards, making it a
> board-specific property rather than a policy directive.
> 
> By providing a precise representation of the time available for less
> critical actions post an under-voltage event, this property enables the
> kernel to make informed decisions on action prioritization, ensuring
> that essential preventative measures are taken to avoid hardware damage
> while also allowing for data capture and analysis.
> 
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
>  .../devicetree/bindings/regulator/regulator.yaml          | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 

Acked-by: Rob Herring <robh@kernel.org>


  reply	other threads:[~2023-10-27 21:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 14:48 [PATCH v4 0/5] regulator: add under-voltage support (part 2) Oleksij Rempel
2023-10-26 14:48 ` [PATCH v4 1/5] regulator: dt-bindings: Add system-critical-regulator property Oleksij Rempel
2023-10-27 21:25   ` Rob Herring
2023-10-26 14:48 ` [PATCH v4 2/5] regulator: Introduce handling for system-critical under-voltage events Oleksij Rempel
2023-10-26 14:48 ` [PATCH v4 3/5] regulator: dt-bindings: Allow system-critical marking for fixed-regulator Oleksij Rempel
2023-10-27 21:24   ` Rob Herring
2023-10-27 21:32     ` Mark Brown
2023-10-30 15:45   ` Rob Herring
2023-10-26 14:48 ` [PATCH v4 4/5] regulator: dt-bindings: Add 'regulator-uv-less-critical-window-ms' property Oleksij Rempel
2023-10-27 21:26   ` Rob Herring [this message]
2023-10-26 14:48 ` [PATCH v4 5/5] regulator: Implement uv_survival_time for handling under-voltage events Oleksij Rempel
2023-11-13 19:40 ` [PATCH v4 0/5] regulator: add under-voltage support (part 2) 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=169844197767.3399644.2264278989526622921.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=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=o.rempel@pengutronix.de \
    --cc=robh+dt@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