From: Guenter Roeck <linux@roeck-us.net>
To: Krzysztof Adamski <krzysztof.adamski@nokia.com>
Cc: Jean Delvare <jdelvare@suse.com>,
Rob Herring <robh+dt@kernel.org>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 4/9] hwmon: (tmp421) support specifying n-factor via DT
Date: Fri, 15 Oct 2021 15:49:59 -0700 [thread overview]
Message-ID: <20211015224959.GA1484958@roeck-us.net> (raw)
In-Reply-To: <69d0bfcc5ba27c67f21d3eabfb100656a14c75b9.1634206677.git.krzysztof.adamski@nokia.com>
On Thu, Oct 14, 2021 at 03:01:28PM +0200, Krzysztof Adamski wrote:
> Previous patches added a way to specify some channel specific parameters
> in DT and n-factor is definitely one of them. This calibration mechanism
> is board specific as its value depends on the diodes/transistors being
> connected to the sensor and thus the DT seems like a right fit for that
> information. It is very similar to the value of shunt resistor that some
> drivers allows specifying in DT.
>
> This patch adds a possibility to set n-factor for each channel via
> "n-factor" DT property in each channel subnode.
>
> Signed-off-by: Krzysztof Adamski <krzysztof.adamski@nokia.com>
Applied, after "s/^ / /"
Guenter
> ---
> drivers/hwmon/tmp421.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/drivers/hwmon/tmp421.c b/drivers/hwmon/tmp421.c
> index af08bc985a13..606914f20910 100644
> --- a/drivers/hwmon/tmp421.c
> +++ b/drivers/hwmon/tmp421.c
> @@ -34,6 +34,7 @@ enum chips { tmp421, tmp422, tmp423, tmp441, tmp442 };
> #define TMP421_STATUS_REG 0x08
> #define TMP421_CONFIG_REG_1 0x09
> #define TMP421_CONVERSION_RATE_REG 0x0B
> +#define TMP421_N_FACTOR_REG_1 0x21
> #define TMP421_MANUFACTURER_ID_REG 0xFE
> #define TMP421_DEVICE_ID_REG 0xFF
>
> @@ -310,6 +311,7 @@ static int tmp421_probe_child_from_dt(struct i2c_client *client,
> {
> struct device *dev = &client->dev;
> u32 i;
> + s32 val;
> int err;
>
> err = of_property_read_u32(child, "reg", &i);
> @@ -329,6 +331,22 @@ static int tmp421_probe_child_from_dt(struct i2c_client *client,
>
> data->channel[i].enabled = of_device_is_available(child);
>
> + err = of_property_read_s32(child, "ti,n-factor", &val);
> + if (!err) {
> + if (i == 0) {
> + dev_err(dev, "n-factor can't be set for internal channel\n");
> + return -EINVAL;
> + }
> +
> + if (val > 127 || val < -128) {
> + dev_err(dev, "n-factor for channel %d invalid (%d)\n",
> + i, val);
> + return -EINVAL;
> + }
> + i2c_smbus_write_byte_data(client, TMP421_N_FACTOR_REG_1 + i - 1,
> + val);
> + }
> +
> return 0;
> }
>
next prev parent reply other threads:[~2021-10-15 22:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 13:00 [PATCH v5 0/9] Add per channel properies support in tmp421 Krzysztof Adamski
2021-10-14 13:00 ` [PATCH v5 1/9] dt-bindings: hwmon: add missing tmp421 binding Krzysztof Adamski
2021-10-14 16:31 ` Rob Herring
2021-10-15 22:29 ` Guenter Roeck
2021-10-14 13:00 ` [PATCH v5 2/9] hwmon: (tmp421) add support for defining labels from DT Krzysztof Adamski
2021-10-15 22:45 ` Guenter Roeck
2021-10-14 13:01 ` [PATCH v5 3/9] hwmon: (tmp421) support disabling channels " Krzysztof Adamski
2021-10-15 22:47 ` Guenter Roeck
2021-10-17 0:00 ` Krzysztof Adamski
2021-10-14 13:01 ` [PATCH v5 4/9] hwmon: (tmp421) support specifying n-factor via DT Krzysztof Adamski
2021-10-15 22:49 ` Guenter Roeck [this message]
2021-10-14 13:09 ` [PATCH v5 5/9] hwmon: (tmp421) really disable channels Krzysztof Adamski
2021-10-15 22:53 ` Guenter Roeck
2021-10-14 13:09 ` [PATCH v5 6/9] hwmon: (tmp421) support HWMON_T_ENABLE Krzysztof Adamski
2021-10-15 22:53 ` Guenter Roeck
2021-10-14 13:10 ` [PATCH v5 7/9] hwmon: (tmp421) update documentation Krzysztof Adamski
2021-10-15 22:54 ` Guenter Roeck
2021-10-14 13:11 ` [PATCH v5 8/9] hwmon: (tmp421) ignore non-channel related DT nodes Krzysztof Adamski
2021-10-15 22:56 ` Guenter Roeck
2021-10-14 13:11 ` [PATCH v5 9/9] dt-bindings: hwmon: allow specifying channels for tmp421 Krzysztof Adamski
2021-10-14 16:31 ` Rob Herring
2021-10-15 22:57 ` 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=20211015224959.GA1484958@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).