All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Qiu <xqiu@google.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Hardware Monitoring <linux-hwmon@vger.kernel.org>,
	Jean Delvare <jdelvare@suse.com>
Subject: Re: [PATCH] hwmon: (pmbus) Improve initialization of 'currpage' and 'currphase'
Date: Thu, 7 May 2020 13:19:58 -0700	[thread overview]
Message-ID: <CAA_a9x+HokYr+kTVfE-tqpztwJRF78bD-YA9TDAak41V81oPoA@mail.gmail.com> (raw)
In-Reply-To: <20200507174407.36576-1-linux@roeck-us.net>

Hi Guenter,

LGTM; minor nits:

On Thu, May 7, 2020 at 10:44 AM Guenter Roeck <linux@roeck-us.net> wrote:
>
> The 'currpage' and 'currphase' variables in struct pmbus_data are used by
> the PMBus core to determine if the phase or page value has changed. Both
> are initialized with values which are never expected to be set in the code
> to ensure that the first page/phase write operation is actually performed.
>
> This is not well explained and occasionally causes confusion. Change the
> type of both variables to s16 and initialize with -1 to ensure that the
> initial value never matches a requested value, and clarify that this
> value means "unknown/unset".
>
> Cc: Alex Qiu <xqiu@google.com>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
>  drivers/hwmon/pmbus/pmbus_core.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/hwmon/pmbus/pmbus_core.c b/drivers/hwmon/pmbus/pmbus_core.c
> index 8d321bf7d15b..a420877ba533 100644
> --- a/drivers/hwmon/pmbus/pmbus_core.c
> +++ b/drivers/hwmon/pmbus/pmbus_core.c
> @@ -109,8 +109,8 @@ struct pmbus_data {
>         bool has_status_word;           /* device uses STATUS_WORD register */
>         int (*read_status)(struct i2c_client *client, int page);
>
> -       u8 currpage;
> -       u8 currphase;   /* current phase, 0xff for all */
> +       s16 currpage;   /* current page, -1 for unknown/unset */
> +       s16 currphase;  /* current phase, 0xff for all, -1 for unknown/unset */
I'm not sure if assigning macros for -1 and 0xff would be a good idea?
>  };
>
>  struct pmbus_debugfs_entry {
> @@ -2529,8 +2529,8 @@ int pmbus_do_probe(struct i2c_client *client, const struct i2c_device_id *id,
>         if (pdata)
>                 data->flags = pdata->flags;
>         data->info = info;
> -       data->currpage = 0xff;
> -       data->currphase = 0xfe;
> +       data->currpage = -1;
> +       data->currphase = -1;
>
>         ret = pmbus_init_common(client, data, info);
>         if (ret < 0)
> --
> 2.17.1
>

Thx!

- Alex Qiu

  reply	other threads:[~2020-05-07 20:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 17:44 [PATCH] hwmon: (pmbus) Improve initialization of 'currpage' and 'currphase' Guenter Roeck
2020-05-07 20:19 ` Alex Qiu [this message]
2020-05-07 20:55   ` Guenter Roeck

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=CAA_a9x+HokYr+kTVfE-tqpztwJRF78bD-YA9TDAak41V81oPoA@mail.gmail.com \
    --to=xqiu@google.com \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux@roeck-us.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.