From: "Kurt Borja" <kuurtb@gmail.com>
To: "Guenter Roeck" <linux@roeck-us.net>,
"Jean Delvare" <jdelvare@suse.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: <stable@vger.kernel.org>, <linux-hwmon@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/3] hwmon: (sht21) Add support for all sht2x chips
Date: Sun, 07 Sep 2025 17:45:43 -0500 [thread overview]
Message-ID: <DCMXLEBY7Z30.20SQGDLMZPYJS@gmail.com> (raw)
In-Reply-To: <6d385692-a4be-4fce-9628-274f95fb24ba@roeck-us.net>
On Sun Sep 7, 2025 at 5:19 PM -05, Guenter Roeck wrote:
> On 9/7/25 15:06, Kurt Borja wrote:
>> All sht2x chips share the same communication protocol so add support for
>> them.
>>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
>> ---
>> Documentation/hwmon/sht21.rst | 11 +++++++++++
>> drivers/hwmon/sht21.c | 3 +++
>> 2 files changed, 14 insertions(+)
>>
>> diff --git a/Documentation/hwmon/sht21.rst b/Documentation/hwmon/sht21.rst
>> index 1bccc8e8aac8d3532ec17dcdbc6a172102877085..65f85ca68ecac1cba6ad23f783fd648305c40927 100644
>> --- a/Documentation/hwmon/sht21.rst
>> +++ b/Documentation/hwmon/sht21.rst
>> @@ -2,6 +2,17 @@ Kernel driver sht21
>> ===================
>>
>> Supported chips:
>> + * Sensirion SHT20
>> +
>> + Prefix: 'sht20'
>> +
>> + Addresses scanned: none
>> +
>> + Datasheet: Publicly available at the Sensirion website
>> +
>> + https://www.sensirion.com/file/datasheet_sht20
>> +
>> +
>
> Too many empty lines.
The next entries are also separated by 3 lines. I did it like that for
symmetry.
>
> Please add SHT20 to Kconfig as well.
Sure!
>
>>
>> * Sensirion SHT21
>>
>> diff --git a/drivers/hwmon/sht21.c b/drivers/hwmon/sht21.c
>> index 97327313529b467ed89d8f6b06c2d78efd54efbf..a2748659edc262dac9d87771f849a4fc0a29d981 100644
>> --- a/drivers/hwmon/sht21.c
>> +++ b/drivers/hwmon/sht21.c
>> @@ -275,7 +275,10 @@ static int sht21_probe(struct i2c_client *client)
>>
>> /* Device ID table */
>> static const struct i2c_device_id sht21_id[] = {
>> + { "sht20" },
>> { "sht21" },
>> + { "sht25" },
>> + { "sht2x" },
>
> AFAICS there is no sht2x chip.
>
>
>> { }
>> };
>> MODULE_DEVICE_TABLE(i2c, sht21_id);
>>
--
~ Kurt
next prev parent reply other threads:[~2025-09-07 22:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 22:06 [PATCH 0/3] hwmon: (sht21) Add devicetree support Kurt Borja
2025-09-07 22:06 ` [PATCH 1/3] hwmon: (sht21) Add support for all sht2x chips Kurt Borja
2025-09-07 22:19 ` Guenter Roeck
2025-09-07 22:45 ` Kurt Borja [this message]
2025-09-07 22:54 ` Guenter Roeck
2025-09-07 22:06 ` [PATCH 2/3] hwmon: (sht21) Add devicetree support Kurt Borja
2025-09-07 22:19 ` Guenter Roeck
2025-09-07 22:48 ` Kurt Borja
2025-09-07 22:06 ` [PATCH 3/3] dt-bindings: trivial-devices: Add sht2x sensors Kurt Borja
2025-09-07 22:20 ` 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=DCMXLEBY7Z30.20SQGDLMZPYJS@gmail.com \
--to=kuurtb@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
--cc=stable@vger.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).