linux-hwmon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Eddie James <eajames@linux.ibm.com>, linux-hwmon@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, jdelvare@suse.com, bjwyman@gmail.com
Subject: Re: [PATCH 1/2] hwmon: (pmbus) Add a NO_PEC flag to probe chips with faulty CAPABILITY
Date: Mon, 21 Dec 2020 08:54:13 -0800	[thread overview]
Message-ID: <f96ded73-93de-dc7d-36af-7f100e71817a@roeck-us.net> (raw)
In-Reply-To: <20201221163058.33257-2-eajames@linux.ibm.com>

On 12/21/20 8:30 AM, Eddie James wrote:
> Some PMBus chips don't respond with valid data when reading the
> CAPABILITY register. For instance the register may report that the
> chip supports PEC when in reality it does not. For such chips, PEC
> must not be enabled while probing the chip, so add a flag so that
> device drivers can force PEC off.
> 

I think the flag should indicate that the capability register
shall not be read/used. That the capability register is currently
only used to check for PEC is secondary. We might,for example,
start using it to check for alert support or to check the numeric
format.

Thanks,
Guenter

> Signed-off-by: Eddie James <eajames@linux.ibm.com>
> ---
>  drivers/hwmon/pmbus/pmbus_core.c |  8 +++++---
>  include/linux/pmbus.h            | 10 ++++++++++
>  2 files changed, 15 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/hwmon/pmbus/pmbus_core.c b/drivers/hwmon/pmbus/pmbus_core.c
> index 192442b3b7a2..3de1657dde35 100644
> --- a/drivers/hwmon/pmbus/pmbus_core.c
> +++ b/drivers/hwmon/pmbus/pmbus_core.c
> @@ -2204,9 +2204,11 @@ static int pmbus_init_common(struct i2c_client *client, struct pmbus_data *data,
>  	}
>  
>  	/* Enable PEC if the controller supports it */
> -	ret = i2c_smbus_read_byte_data(client, PMBUS_CAPABILITY);
> -	if (ret >= 0 && (ret & PB_CAPABILITY_ERROR_CHECK))
> -		client->flags |= I2C_CLIENT_PEC;
> +	if (!(data->flags & PMBUS_NO_PEC)) {
> +		ret = i2c_smbus_read_byte_data(client, PMBUS_CAPABILITY);
> +		if (ret >= 0 && (ret & PB_CAPABILITY_ERROR_CHECK))
> +			client->flags |= I2C_CLIENT_PEC;
> +	}
>  
>  	/*
>  	 * Check if the chip is write protected. If it is, we can not clear
> diff --git a/include/linux/pmbus.h b/include/linux/pmbus.h
> index 1ea5bae708a1..9bdc8a581b03 100644
> --- a/include/linux/pmbus.h
> +++ b/include/linux/pmbus.h
> @@ -34,6 +34,16 @@
>   */
>  #define PMBUS_WRITE_PROTECTED	BIT(1)
>  
> +/*
> + * PMBUS_NO_PEC
> + *
> + * Some PMBus chips don't respond with valid data when reading the CAPABILITY
> + * register. In this case, the register may report that the chip supports PEC
> + * with bit 7 (PB_CAPABILITY_ERROR_CHECK) when in reality it's not supported.
> + * For such chips, PEC must not be enabled before probing the chip.
> + */
> +#define PMBUS_NO_PEC			BIT(2)
> +
>  struct pmbus_platform_data {
>  	u32 flags;		/* Device specific flags */
>  
> 


  reply	other threads:[~2020-12-21 18:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-21 16:30 [PATCH 0/2] hwmon: (pmbus) Add a NO_PEC flag to probe chips with faulty CAPABILITY Eddie James
2020-12-21 16:30 ` [PATCH 1/2] " Eddie James
2020-12-21 16:54   ` Guenter Roeck [this message]
2020-12-21 18:32     ` Eddie James
2020-12-21 18:53       ` Guenter Roeck
2020-12-21 16:30 ` [PATCH 2/2] hwmon: (pmbus/ibm-cffps) Set the PMBUS_NO_PEC flag Eddie James

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=f96ded73-93de-dc7d-36af-7f100e71817a@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=bjwyman@gmail.com \
    --cc=eajames@linux.ibm.com \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).