From: Guenter Roeck <linux@roeck-us.net>
To: Conor Dooley <conor@kernel.org>, Marek Vasut <marex@nabladev.com>
Cc: linux-pm@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Flaviu Nistor <flaviu.nistor@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: hwmon: tmp102: Document TMP113
Date: Tue, 1 Sep 2026 10:48:54 -0700 [thread overview]
Message-ID: <4bbcc5fe-86a1-4299-a0df-e9f44d5c237f@roeck-us.net> (raw)
In-Reply-To: <20260901-untimely-wake-578b1a86b9fe@spud>
On 9/1/26 10:37, Conor Dooley wrote:
> On Tue, Sep 01, 2026 at 06:09:20PM +0200, Marek Vasut wrote:
>> The TMP113 temperature sensor part is register compatible with TMP102,
>> document it using a fallback compatible. Unlike TMP102 and TMP110, the
>> TMP113 does have additional unique ID registers, it is up to the driver
>> to handle those.
>>
>> Signed-off-by: Marek Vasut <marex@nabladev.com>
>> ---
>> Cc: Conor Dooley <conor+dt@kernel.org>
>> Cc: Flaviu Nistor <flaviu.nistor@gmail.com>
>> Cc: Guenter Roeck <linux@roeck-us.net>
>> Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
>> Cc: Rob Herring <robh@kernel.org>
>> Cc: devicetree@vger.kernel.org
>> Cc: linux-hwmon@vger.kernel.org
>> Cc: linux-kernel@vger.kernel.org
>> ---
>> V2: Rebase on current next and resend, resolve a conflict with commit
>> d67ec24d3f07 ("dt-bindings: hwmon: tmp102: move ti,tmp103 out of trivial-devices.yaml")
>> Note that the TMP102,110,113 are backward compatible, therefore the
>> valid compatible strings are:
>> - "ti,tmp110", "ti,tmp102"
>> - "ti,tmp113", "ti,tmp102"
>> - "ti,tmp102"
>> The TMP103 is not backward compatible, it only shares bindings now,
>> therefore the only valid compatible string for the TMP103 should be:
>> - "ti,tmp103"
>> And that is all, no other compatible strings are acceptable here.
>> ---
>> .../devicetree/bindings/hwmon/ti,tmp102.yaml | 11 ++++++-----
>> 1 file changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/hwmon/ti,tmp102.yaml b/Documentation/devicetree/bindings/hwmon/ti,tmp102.yaml
>> index 55d9f106465d7..c0b747a9ce0de 100644
>> --- a/Documentation/devicetree/bindings/hwmon/ti,tmp102.yaml
>> +++ b/Documentation/devicetree/bindings/hwmon/ti,tmp102.yaml
>> @@ -4,7 +4,7 @@
>> $id: http://devicetree.org/schemas/hwmon/ti,tmp102.yaml#
>> $schema: http://devicetree.org/meta-schemas/core.yaml#
>>
>> -title: TMP102/TMP103/TMP110 temperature sensor
>> +title: TMP102/TMP103/TMP110/TMP113 temperature sensor
>>
>> maintainers:
>> - Krzysztof Kozlowski <krzk@kernel.org>
>> @@ -13,11 +13,12 @@ properties:
>> compatible:
>> oneOf:
>> - items:
>> + - enum:
>> + - ti,tmp110
>> + - ti,tmp113
>> - const: ti,tmp102
>> - - const: ti,tmp103
>> - - const: ti,tmp110
>> - - enum:
>> - - ti,tmp102
>> + - const: ti,tmp102
>> + - const: ti,tmp103
>
> Should this not be two patches, one fixing the existing stuff and one
> adding the 113?
>
It is all in -next. Looks like I resolved the conflict when combining
"dt-bindings: hwmon: tmp102: move ti,tmp103 out of trivial-devices.yaml"
and "dt-bindings: hwmon: tmp102: Document TMP110" the wrong way.
Sorry for that.
Instead of adding more patches on top of it, how about providing a
single patch moving tmp103 and adding tmp110 as well as tmp113
together ? Alternatively, I could drop "dt-bindings: hwmon: tmp102:
Document TMP110", apply the original (non-conflicting version) of
"dt-bindings: hwmon: tmp102: move ti,tmp103 out of trivial-devices.yaml",
and then tmp110 and tmp113 could be added in a single patch.
Please let me know.
Thanks,
Guenter
next prev parent reply other threads:[~2026-09-01 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 16:09 [PATCH v2] dt-bindings: hwmon: tmp102: Document TMP113 Marek Vasut
2026-09-01 16:14 ` sashiko-bot
2026-09-01 17:37 ` Conor Dooley
2026-09-01 17:47 ` Marek Vasut
2026-09-01 17:48 ` Guenter Roeck [this message]
2026-09-01 17:58 ` Marek Vasut
2026-09-01 18:04 ` Conor Dooley
2026-09-01 18:16 ` 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=4bbcc5fe-86a1-4299-a0df-e9f44d5c237f@roeck-us.net \
--to=linux@roeck-us.net \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=flaviu.nistor@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marex@nabladev.com \
--cc=robh@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