From: Guenter Roeck <linux@roeck-us.net>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: devicetree@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
Patrick Rudolph <patrick.rudolph@9elements.com>
Subject: Re: [PATCH v3 1/4] hwmon: (pmbus/core): Add status byte to regulator flag map
Date: Wed, 30 Nov 2022 10:06:42 -0800 [thread overview]
Message-ID: <20221130180642.GA2656856@roeck-us.net> (raw)
In-Reply-To: <20221130165833.3478555-1-Naresh.Solanki@9elements.com>
On Wed, Nov 30, 2022 at 05:58:28PM +0100, Naresh Solanki wrote:
> Add PMBus status byte to regulator flag map.
>
> Signed-off-by: Naresh Solanki <Naresh.Solanki@9elements.com>
>
> ---
> Changes:
> - Remove status input
Not really.
> - Add comment for PMBUS status byte.
> ---
> drivers/hwmon/pmbus/pmbus_core.c | 20 +++++++++++---------
> 1 file changed, 11 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/hwmon/pmbus/pmbus_core.c b/drivers/hwmon/pmbus/pmbus_core.c
> index 95e95783972a..a7b4ae0f1f3b 100644
> --- a/drivers/hwmon/pmbus/pmbus_core.c
> +++ b/drivers/hwmon/pmbus/pmbus_core.c
> @@ -2751,7 +2751,16 @@ struct pmbus_regulator_status_category {
> };
>
> static const struct pmbus_regulator_status_category pmbus_regulator_flag_map[] = {
> - {
> + { /* STATUS byte is always present. */
> + .func = -1,
> + .reg = PMBUS_STATUS_BYTE,
> + .bits = (const struct pmbus_regulator_status_assoc[]) {
> + { PB_STATUS_IOUT_OC, REGULATOR_ERROR_OVER_CURRENT },
> + { PB_STATUS_VOUT_OV, REGULATOR_ERROR_REGULATION_OUT },
> + { PB_STATUS_VIN_UV, REGULATOR_ERROR_UNDER_VOLTAGE },
Still there.
> + { },
> + },
> + }, {
> .func = PMBUS_HAVE_STATUS_VOUT,
> .reg = PMBUS_STATUS_VOUT,
> .bits = (const struct pmbus_regulator_status_assoc[]) {
> @@ -2768,6 +2777,7 @@ static const struct pmbus_regulator_status_category pmbus_regulator_flag_map[] =
> { PB_IOUT_OC_WARNING, REGULATOR_ERROR_OVER_CURRENT_WARN },
> { PB_IOUT_OC_FAULT, REGULATOR_ERROR_OVER_CURRENT },
> { PB_IOUT_OC_LV_FAULT, REGULATOR_ERROR_OVER_CURRENT },
> + { PB_POUT_OP_FAULT, REGULATOR_ERROR_FAIL },
Please document your changes in the description. There are two functional
changes hidden under "Add PMBus status byte to regulator flag map".
That is inappropriate. Those, as I have pointed out, should be separate
patches.
Guenter
> { },
> },
> }, {
> @@ -2834,14 +2844,6 @@ static int pmbus_regulator_get_error_flags(struct regulator_dev *rdev, unsigned
> if (status & PB_STATUS_POWER_GOOD_N)
> *flags |= REGULATOR_ERROR_REGULATION_OUT;
> }
> - /*
> - * Unlike most other status bits, PB_STATUS_{IOUT_OC,VOUT_OV} are
> - * defined strictly as fault indicators (not warnings).
> - */
> - if (status & PB_STATUS_IOUT_OC)
> - *flags |= REGULATOR_ERROR_OVER_CURRENT;
> - if (status & PB_STATUS_VOUT_OV)
> - *flags |= REGULATOR_ERROR_REGULATION_OUT;
>
> /*
> * If we haven't discovered any thermal faults or warnings via
>
> base-commit: 9494c53e1389b120ba461899207ac8a3aab2632c
> --
> 2.37.3
>
next prev parent reply other threads:[~2022-11-30 18:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 16:58 [PATCH v3 1/4] hwmon: (pmbus/core): Add status byte to regulator flag map Naresh Solanki
2022-11-30 16:58 ` [PATCH v3 1/4] hwmon: (pmbus/core): Update " Naresh Solanki
2022-11-30 18:09 ` Guenter Roeck
2022-11-30 18:15 ` Naresh Solanki
2022-11-30 18:06 ` Guenter Roeck [this message]
2022-11-30 18:12 ` [PATCH v3 1/4] hwmon: (pmbus/core): Add status byte to " Naresh Solanki
2022-11-30 18:19 ` Guenter Roeck
2022-11-30 18:25 ` Naresh Solanki
-- strict thread matches above, loose matches on Subject: below --
2022-11-30 16:59 Naresh Solanki
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=20221130180642.GA2656856@roeck-us.net \
--to=linux@roeck-us.net \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=lgirdwood@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.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).