devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>, "Sung-Chi, Li" <lschyi@chromium.org>
Cc: "Conor Dooley" <conor.dooley@microchip.com>,
	"Lee Jones" <lee@kernel.org>, "Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Benson Leung" <bleung@chromium.org>,
	"Guenter Roeck" <groeck@chromium.org>,
	"Thomas Weißschuh" <thomas@weissschuh.net>,
	"Jean Delvare" <jdelvare@suse.com>,
	devicetree@vger.kernel.org, chrome-platform@lists.linux.dev,
	linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v3 2/2] dt-bindings: mfd: Add properties for thermal sensor cells
Date: Mon, 25 Nov 2024 09:54:48 +0100	[thread overview]
Message-ID: <1c1604b7-baf2-466d-a46c-4ed8d407ed9c@kernel.org> (raw)
In-Reply-To: <eb1c249c-5f42-4878-8934-09d6ea5c43f2@kernel.org>

On 25/11/2024 09:52, Krzysztof Kozlowski wrote:
> On 13/11/2024 04:05, Guenter Roeck wrote:
>> On 11/12/24 18:39, Sung-Chi, Li wrote:
>>> The cros_ec supports reading thermal values from thermal sensors
>>> connect to it. Add the property '#thermal-sensor-cells' bindings, such
>>> that thermal framework can recognize cros_ec as a valid thermal device.
>>>
>>> Signed-off-by: Sung-Chi, Li <lschyi@chromium.org>
>>> Acked-by: Conor Dooley <conor.dooley@microchip.com>
>>> ---
>>>   Changes in v2:
>>>     - Add changes for DTS binding.
>>>   Changes in v3:
>>>     - Remove unneeded Change-Id tag in commit message.
>>> ---
>>
>> I can't apply this one (not in hwmon space), so
>>
>> Acked-by: Guenter Roeck <linux@roeck-us.net>
>>
>> with the assumption that Lee will pick it up.
> 
> This was merged, while I was AFK, so the ship has sailed, but let me
> state here objection for any future discussions:
> 
> NAK, this is not a thermal sensor. The commit msg explains what they
> want to achieve, but that's not a valid reason to add property from
> different class of devices.
> 
> This is some hardware/temperature monitoring device or power supply, not
> part of SoC, not integrated into any SoC thermal zone. Calling it
> thermal sensor is huge stretch and inappropriate hardware description
> leading to next patches like calling it a SoC cooling device, instead of
> simple power supply (for which we have bindings!).
Ah, wait, this was not merged, so I can actually NAK it.

BTW, all your patches are incorrectly ordered - bindings are always
before the users. You cannot merge user of a binding without or before
the binding.

Best regards,
Krzysztof

  reply	other threads:[~2024-11-25  8:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241111074904.1059268-1-lschyi@chromium.org>
2024-11-11  9:50 ` [PATCH v2] hwmon: (cros_ec) register thermal sensors to thermal framework Sung-Chi
2024-11-11  9:50   ` [PATCH v2 2/2] dt-bindings: mfd: Add properties for thermal sensor cells Sung-Chi
2024-11-11 20:08     ` Conor Dooley
2024-11-11 16:30   ` [PATCH v2] hwmon: (cros_ec) register thermal sensors to thermal framework Thomas Weißschuh
2024-11-11 17:01   ` Guenter Roeck
2024-11-12  7:42     ` Sung-Chi, Li
2024-11-13  2:39 ` [PATCH v3 1/2] " Sung-Chi, Li
2024-11-13  2:39   ` [PATCH v3 2/2] dt-bindings: mfd: Add properties for thermal sensor cells Sung-Chi, Li
2024-11-13  3:05     ` Guenter Roeck
2024-11-25  8:52       ` Krzysztof Kozlowski
2024-11-25  8:54         ` Krzysztof Kozlowski [this message]
2024-11-25 15:13         ` Guenter Roeck
2024-11-25 15:18           ` Krzysztof Kozlowski
2024-11-25 16:41             ` Guenter Roeck
2024-11-25 17:12               ` Krzysztof Kozlowski
2024-11-13  3:04   ` [PATCH v3 1/2] hwmon: (cros_ec) register thermal sensors to thermal framework 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=1c1604b7-baf2-466d-a46c-4ed8d407ed9c@kernel.org \
    --to=krzk@kernel.org \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=groeck@chromium.org \
    --cc=jdelvare@suse.com \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lschyi@chromium.org \
    --cc=robh@kernel.org \
    --cc=thomas@weissschuh.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).