From: Guenter Roeck <linux@roeck-us.net>
To: Zev Weiss <zev@bewilderbeest.net>
Cc: linux-hwmon@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
Denis Pauk <pauk.denis@gmail.com>,
linux-kernel@vger.kernel.org, Renze Nicolai <renze@rnplus.nl>
Subject: Re: [PATCH v3] hwmon: (nct6775) add support for TSI temperature registers
Date: Wed, 12 Jan 2022 08:47:29 -0800 [thread overview]
Message-ID: <20220112164729.GA399472@roeck-us.net> (raw)
In-Reply-To: <20220112034824.3467-1-zev@bewilderbeest.net>
On Tue, Jan 11, 2022 at 07:48:24PM -0800, Zev Weiss wrote:
> These registers report CPU temperatures (and, depending on the system,
> sometimes chipset temperatures) via the TSI interface on AMD systems.
> They're distinct from most of the other Super-IO temperature readings
> (CPUTIN, SYSTIN, etc.) in that they're not a selectable source for
> monitoring and are in a different (higher resolution) format, but can
> still provide useful temperature data.
>
> Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
> Tested-by: Renze Nicolai <renze@rnplus.nl>
> ---
>
[ ... ]
> + switch (data->kind) {
> + case nct6791:
> + case nct6792:
> + case nct6793:
> + data->REG_TSI_TEMP = NCT6776_REG_TSI_TEMP;
> + num_reg_tsi_temp = ARRAY_SIZE(NCT6776_REG_TSI_TEMP);
> + break;
> + case nct6795:
> + case nct6796:
> + case nct6797:
> + case nct6798:
> + data->REG_TSI_TEMP = NCT6796_REG_TSI_TEMP;
> + num_reg_tsi_temp = ARRAY_SIZE(NCT6796_REG_TSI_TEMP);
> + break;
> + default:
> + dev_warn(dev, "unknown number of TSI temp registers for %s\n", data->name);
> + num_reg_tsi_temp = 0;
> + break;
Please drop the message. This is new functionality which should not
suddenly produce a warning for chips which possibly do not support those
registers in the first place. For users with those chips the warning
is just confusing.
Guenter
next prev parent reply other threads:[~2022-01-12 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 3:48 Zev Weiss
2022-01-12 16:47 ` Guenter Roeck [this message]
2022-01-13 11:16 ` Zev Weiss
2022-01-13 14:51 ` 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=20220112164729.GA399472@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pauk.denis@gmail.com \
--cc=renze@rnplus.nl \
--cc=zev@bewilderbeest.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome