From: Guenter Roeck <linux@roeck-us.net>
To: "Mårten Lindahl" <marten.lindahl@axis.com>
Cc: Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, kernel@axis.com
Subject: Re: [PATCH v4 3/4] hwmon: (pmbus/ltc2978) Add chip specific write_byte_data
Date: Sun, 1 May 2022 21:24:34 -0700 [thread overview]
Message-ID: <20220502042434.GA1717760@roeck-us.net> (raw)
In-Reply-To: <20220428144039.2464667-4-marten.lindahl@axis.com>
On Thu, Apr 28, 2022 at 04:40:38PM +0200, Mårten Lindahl wrote:
> Several of the manuals for devices supported by this driver describes
> the need for a minimum wait time before the chip is ready to receive
> next command.
>
> This wait time is already implemented in the driver as a ltc_wait_ready
> function with a driver defined wait time of 100 ms, and is considered
> for specific devices before reading/writing data on the pmbus.
>
> Since this driver uses the default pmbus_regulator_ops for the enable/
> disable/is_enabled functions we should add a driver specific callback
> for write_byte_data to prevent bypassing the wait time recommendations
> for the following devices: ltc3880/ltc3882/ltc3883/ltc3884/ltc3886/
> ltc3887/ltc3889/ltm4664/ltm4675/ltm4676/ltm4677/ltm4678/ltm4680/ltm4686/
> ltm4700/ltc7880.
>
> Signed-off-by: Mårten Lindahl <marten.lindahl@axis.com>
Applied.
Thanks,
Guenter
> ---
> drivers/hwmon/pmbus/ltc2978.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/hwmon/pmbus/ltc2978.c b/drivers/hwmon/pmbus/ltc2978.c
> index 0127273883f0..531aa674a928 100644
> --- a/drivers/hwmon/pmbus/ltc2978.c
> +++ b/drivers/hwmon/pmbus/ltc2978.c
> @@ -196,6 +196,17 @@ static int ltc_read_byte_data(struct i2c_client *client, int page, int reg)
> return pmbus_read_byte_data(client, page, reg);
> }
>
> +static int ltc_write_byte_data(struct i2c_client *client, int page, int reg, u8 value)
> +{
> + int ret;
> +
> + ret = ltc_wait_ready(client);
> + if (ret < 0)
> + return ret;
> +
> + return pmbus_write_byte_data(client, page, reg, value);
> +}
> +
> static int ltc_write_byte(struct i2c_client *client, int page, u8 byte)
> {
> int ret;
> @@ -681,6 +692,7 @@ static int ltc2978_probe(struct i2c_client *client)
> info = &data->info;
> info->write_word_data = ltc2978_write_word_data;
> info->write_byte = ltc_write_byte;
> + info->write_byte_data = ltc_write_byte_data;
> info->read_word_data = ltc_read_word_data;
> info->read_byte_data = ltc_read_byte_data;
>
next prev parent reply other threads:[~2022-05-02 4:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 14:40 [PATCH v4 0/4] hwmon: (pmbus/ltc2978) Add regulator ops Mårten Lindahl
2022-04-28 14:40 ` [PATCH v4 1/4] hwmon: (pmbus) Introduce and use write_byte_data callback Mårten Lindahl
2022-05-02 4:23 ` Guenter Roeck
2022-04-28 14:40 ` [PATCH v4 2/4] hwmon: (pmbus) Use _pmbus_read_byte_data with callback Mårten Lindahl
2022-05-02 4:24 ` Guenter Roeck
2022-04-28 14:40 ` [PATCH v4 3/4] hwmon: (pmbus/ltc2978) Add chip specific write_byte_data Mårten Lindahl
2022-05-02 4:24 ` Guenter Roeck [this message]
2022-04-28 14:40 ` [PATCH v4 4/4] hwmon: (pmbus) Add get_voltage/set_voltage ops Mårten Lindahl
2022-04-28 16:49 ` Guenter Roeck
2022-04-29 9:52 ` Marten Lindahl
2022-04-29 17:00 ` Guenter Roeck
2022-05-02 10:42 ` Marten Lindahl
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=20220502042434.GA1717760@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jdelvare@suse.com \
--cc=kernel@axis.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=marten.lindahl@axis.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