From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Zev Weiss <zev@bewilderbeest.net>
Cc: Guenter Roeck <linux@roeck-us.net>,
Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Renze Nicolai <renze@rnplus.nl>,
Oleksandr Natalenko <oleksandr@natalenko.name>,
openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/7] dt-bindings: hwmon: Add nuvoton,nct6775
Date: Wed, 27 Apr 2022 09:00:36 +0200 [thread overview]
Message-ID: <a3d9f68d-9101-2749-a7cd-5a4b3595a07a@linaro.org> (raw)
In-Reply-To: <YmjmWNUpCAFYesyk@hatter.bewilderbeest.net>
On 27/04/2022 08:44, Zev Weiss wrote:
>
>>> + maximum: 0xff
>>> + default: 0
>>
>> Since by default it is disabled, doesn't it make a required property?
>> IOW, if you add a node without this mask, will the device operate
>> properly and usefully?
>>
>
> Yeah, zero active TSI channels is a totally legitimate way for these
> devices to operate. TSI is just an optional source of additional
> temperature readings that's used on some (AMD) systems; all the basic
> Super I/O functionality works fine without it.
OK, thanks.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-27 7:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 1:01 [PATCH v4 0/7] hwmon: (nct6775) Convert to regmap, add i2c support Zev Weiss
2022-04-27 1:01 ` [PATCH v4 1/7] dt-bindings: hwmon: Add nuvoton,nct6775 Zev Weiss
2022-04-27 6:04 ` Krzysztof Kozlowski
2022-04-27 6:44 ` Zev Weiss
2022-04-27 7:00 ` Krzysztof Kozlowski [this message]
2022-04-27 16:37 ` Krzysztof Kozlowski
2022-04-27 20:05 ` Zev Weiss
2022-04-27 14:18 ` Rob Herring
2022-04-27 13:37 ` [PATCH v4 0/7] hwmon: (nct6775) Convert to regmap, add i2c support Guenter Roeck
2022-05-01 15:18 ` Oleksandr Natalenko
2022-05-02 3:50 ` Guenter Roeck
2022-05-02 6:06 ` Oleksandr Natalenko
2022-05-02 18:42 ` 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=a3d9f68d-9101-2749-a7cd-5a4b3595a07a@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=oleksandr@natalenko.name \
--cc=openbmc@lists.ozlabs.org \
--cc=renze@rnplus.nl \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).