From: Guenter Roeck <linux@roeck-us.net>
To: Krzysztof Adamski <krzysztof.adamski@nokia.com>,
Jean Delvare <jdelvare@suse.com>
Cc: Rob Herring <robh+dt@kernel.org>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 7/8] hwmon: (tmp421) really disable channels
Date: Tue, 7 Sep 2021 08:37:03 -0700 [thread overview]
Message-ID: <4392497d-22fe-b9df-cde1-73ff7b6a8d4e@roeck-us.net> (raw)
In-Reply-To: <d0a1be24701dcf19a2f7501a9bc7fddf2b739792.1631021349.git.krzysztof.adamski@nokia.com>
On 9/7/21 6:46 AM, Krzysztof Adamski wrote:
> Recent patch added possibility to disable selected channels. That would
> only make sure that the ENODATA is returned for those channels but would
> not configure the actual hardware.
>
> With this patch, the config register is written to make sure the
> channels are disabled also at hardware level.
>
> Signed-off-by: Krzysztof Adamski <krzysztof.adamski@nokia.com>
> ---
> drivers/hwmon/tmp421.c | 35 ++++++++++++++++++++++++++++++++---
> 1 file changed, 32 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/hwmon/tmp421.c b/drivers/hwmon/tmp421.c
> index 90c6b094785e..cec25fb1c771 100644
> --- a/drivers/hwmon/tmp421.c
> +++ b/drivers/hwmon/tmp421.c
> @@ -33,6 +33,8 @@ enum chips { tmp421, tmp422, tmp423, tmp441, tmp442 };
> /* The TMP421 registers */
> #define TMP421_STATUS_REG 0x08
> #define TMP421_CONFIG_REG_1 0x09
> +#define TMP421_CONFIG_REG_2 0x0A
> +#define TMP421_CONFIG_REG_REN(x) (BIT(3 + (x)))
> #define TMP421_CONVERSION_RATE_REG 0x0B
> #define TMP421_N_FACTOR_REG_1 0x21
> #define TMP421_MANUFACTURER_ID_REG 0xFE
> @@ -351,6 +353,25 @@ void tmp421_probe_from_dt(struct i2c_client *client, struct tmp421_data *data)
> }
> }
>
> +void tmp421_disable_channels(struct i2c_client *client, uint8_t mask)
> +{
> + int err;
> + int cfg = i2c_smbus_read_byte_data(client, TMP421_CONFIG_REG_2);
> +
> + if (cfg < 0) {
> + dev_err(&client->dev,
> + "error reading register, can't disable channels\n");
> + return;
> + }
> +
> + cfg &= ~mask;
> +
> + err = i2c_smbus_write_byte_data(client, TMP421_CONFIG_REG_2, cfg);
> + if (err < 0)
> + dev_err(&client->dev,
> + "error writing register, can't disable channels\n");
> +}
> +
> static const struct hwmon_ops tmp421_ops = {
> .is_visible = tmp421_is_visible,
> .read = tmp421_read,
> @@ -363,6 +384,7 @@ static int tmp421_probe(struct i2c_client *client)
> struct device *hwmon_dev;
> struct tmp421_data *data;
> int i, err;
> + u8 disable = 0;
>
> data = devm_kzalloc(dev, sizeof(struct tmp421_data), GFP_KERNEL);
> if (!data)
> @@ -380,11 +402,18 @@ static int tmp421_probe(struct i2c_client *client)
> if (err)
> return err;
>
> - for (i = 0; i < data->channels; i++)
> - data->temp_config[i] = HWMON_T_INPUT | HWMON_T_FAULT;
> -
> tmp421_probe_from_dt(client, data);
>
> + for (i = 0; i < data->channels; i++) {
> + data->temp_config[i] |= HWMON_T_INPUT | HWMON_T_FAULT;
> + if (data->channel[i].disabled)
> + disable |= TMP421_CONFIG_REG_REN(i);
> +
> + }
> +
> + if (disable)
> + tmp421_disable_channels(client, disable);
> +
This doesn't take into account that channels may already be disabled
by the BIOS/ROMMON. The code will have to set the channel status explicitly
for all channels if configured through dt, or read it from the chip
otherwise. Also, as mentioned, the sysfs attribute should be supported
as well (meaning it should also be possible to enable a channel).
Guenter
> data->chip.ops = &tmp421_ops;
> data->chip.info = data->info;
>
>
next prev parent reply other threads:[~2021-09-07 15:37 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 13:41 [PATCH 0/8] Add per channel properies support in tmp421 Krzysztof Adamski
2021-09-07 13:42 ` [PATCH 1/8] dt-bindings: hwmon: add missing tmp421 binding Krzysztof Adamski
2021-09-20 22:21 ` Rob Herring
2021-09-07 13:42 ` [PATCH 2/8] hwmon: (tmp421) introduce MAX_CHANNELS define Krzysztof Adamski
2021-09-07 13:43 ` [PATCH 3/8] hwmon: (tmp421) introduce a channel struct Krzysztof Adamski
2021-09-07 13:43 ` [PATCH 4/8] hwmon: (tmp421) add support for defining labels from DT Krzysztof Adamski
2021-09-07 15:46 ` Guenter Roeck
2021-09-07 17:49 ` Krzysztof Adamski
2021-09-07 17:55 ` Guenter Roeck
2021-09-07 18:08 ` Krzysztof Adamski
2021-09-07 18:28 ` kernel test robot
2021-09-09 17:29 ` kernel test robot
2021-09-09 17:29 ` [RFC PATCH] hwmon: tmp421_probe_child_from_dt() can be static kernel test robot
2021-09-07 13:43 ` [PATCH 5/8] hwmon: (tmp421) support disabling channels from DT Krzysztof Adamski
2021-09-07 15:33 ` Guenter Roeck
2021-09-07 13:45 ` [PATCH 6/8] hwmon: (tmp421) support specifying n-factor via DT Krzysztof Adamski
2021-09-07 15:42 ` Guenter Roeck
2021-09-07 13:46 ` [PATCH 7/8] hwmon: (tmp421) really disable channels Krzysztof Adamski
2021-09-07 15:37 ` Guenter Roeck [this message]
2021-09-07 19:52 ` kernel test robot
2021-09-09 20:40 ` kernel test robot
2021-09-09 20:40 ` [RFC PATCH] hwmon: tmp421_disable_channels() can be static kernel test robot
2021-09-07 13:46 ` [PATCH 8/8] dt-bindings: hwmon: allow specifying channels for tmp421 Krzysztof Adamski
2021-09-07 15:46 ` Guenter Roeck
2021-09-07 18:04 ` Krzysztof Adamski
2021-09-20 22:24 ` Rob Herring
2021-09-21 12:58 ` Guenter Roeck
2021-09-21 19:06 ` Rob Herring
2021-09-21 20:52 ` Guenter Roeck
2021-09-21 21:21 ` Oskar Senft
2021-09-21 22:03 ` Oskar Senft
2021-09-23 15:30 ` Rob Herring
2021-09-24 0:29 ` Guenter Roeck
2021-09-24 7:53 ` Krzysztof Adamski
2021-09-24 11:46 ` Guenter Roeck
2021-09-24 15:37 ` Oskar Senft
2021-09-25 13:26 ` Guenter Roeck
2021-10-08 12:55 ` Oskar Senft
2021-10-08 13:11 ` Guenter Roeck
2021-09-22 7:22 ` Krzysztof Adamski
2021-09-22 12:39 ` Guenter Roeck
2021-09-22 18:32 ` Krzysztof Adamski
2021-09-23 0:38 ` 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=4392497d-22fe-b9df-cde1-73ff7b6a8d4e@roeck-us.net \
--to=linux@roeck-us.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzysztof.adamski@nokia.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=robh+dt@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).