From: Benjamin Bara <bbara93@gmail.com>
To: broonie@kernel.org
Cc: DLG-Adam.Thomson.Opensource@dm.renesas.com, bbara93@gmail.com,
benjamin.bara@skidata.com, devicetree@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org, lee@kernel.org,
lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
mazziesaccount@gmail.com, robh+dt@kernel.org,
stwiss.opensource@diasemi.com, support.opensource@diasemi.com
Subject: Re: [PATCH v2 2/3] regulator: da9063: implement basic XVP setter
Date: Wed, 5 Apr 2023 16:08:29 +0200 [thread overview]
Message-ID: <20230405140829.602413-1-bbara93@gmail.com> (raw)
In-Reply-To: <35202b81-abd6-4e0b-b2ad-a385cbb3979d@sirena.org.uk>
Thank you for the feedback!
On Wed, 5 Apr 2023 at 12:52, Mark Brown <broonie@kernel.org> wrote:
> I have no idea what a "basic XVP setter" is and this isn't super
> enlightening. Is VP supposed to mean voltage protection or something?
Yes, but basically this series handles just the monitoring part. The
"protection part" is happening in hardware (at least on our board). So I will
reword "XVP" to "voltage monitoring" in the next version.
> I'm not sure that a user is going to figure out that this refers to the
> protection levels, there's no hint as to what the X might be and the error
> suggests that both the under and over voltage protection limits must be have
> the same value, not just both be provided.
I will split up the "catch-all" into an error per severity, like:
"error-microvolt: value must be equal for uv and ov!"
I will also ensure that there is only one severity set per regulator.
Additionally, will also adapt the docu: if the voltage monitor should be
changed, uv and ov must be set to the same severity and value.
next prev parent reply other threads:[~2023-04-05 14:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 5:29 [PATCH v2 0/3] regulator: da9063: disable unused voltage monitors Benjamin Bara
2023-04-05 5:29 ` [PATCH v2 1/3] regulator: da9063: add voltage monitoring registers Benjamin Bara
2023-04-05 7:29 ` Matti Vaittinen
2023-04-05 8:04 ` Benjamin Bara
2023-04-05 5:29 ` [PATCH v2 2/3] regulator: da9063: implement basic XVP setter Benjamin Bara
2023-04-05 7:42 ` Matti Vaittinen
2023-04-05 10:52 ` Mark Brown
2023-04-05 14:08 ` Benjamin Bara [this message]
2023-04-05 5:29 ` [PATCH v2 3/3] dt-bindings: mfd: dlg,da9063: document XVP Benjamin Bara
2023-04-05 5:33 ` Krzysztof Kozlowski
2023-04-05 7:43 ` Matti Vaittinen
2023-04-05 15:30 ` [PATCH v2 0/3] regulator: da9063: disable unused voltage monitors Lee Jones
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=20230405140829.602413-1-bbara93@gmail.com \
--to=bbara93@gmail.com \
--cc=DLG-Adam.Thomson.Opensource@dm.renesas.com \
--cc=benjamin.bara@skidata.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=robh+dt@kernel.org \
--cc=stwiss.opensource@diasemi.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;
as well as URLs for NNTP newsgroup(s).