From: Krzysztof Kozlowski <krzk@kernel.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: thermal: generic-adc: Add optional io-channel-cells property
Date: Tue, 11 Mar 2025 09:20:21 +0100 [thread overview]
Message-ID: <dc772e9e-632f-4c38-a654-833df0800ee1@kernel.org> (raw)
In-Reply-To: <20250310075638.6979-2-clamor95@gmail.com>
On 10/03/2025 08:56, Svyatoslav Ryhel wrote:
> This implements a mechanism to derive temperature values from an existing
> ADC IIO channel, effectively creating a temperature IIO channel. This
> approach avoids adding a new sensor and its associated conversion table,
> while providing IIO-based temperature data for devices that may not utilize
> hwmon.
>
You got comments from Rob few days ago to which you did not respond.
Instead you decided to send next version, which hides the previous
unresolved discussion.
This patch does not look necessary based on earlier discussion.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-11 8:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 7:56 [PATCH v4 0/2] thermal: thermal-generic-adc: add temp sensor function Svyatoslav Ryhel
2025-03-10 7:56 ` [PATCH v4 1/2] dt-bindings: thermal: generic-adc: Add optional io-channel-cells property Svyatoslav Ryhel
2025-03-11 8:20 ` Krzysztof Kozlowski [this message]
2025-03-11 8:30 ` Svyatoslav Ryhel
2025-03-10 7:56 ` [PATCH v4 2/2] thermal: thermal-generic-adc: add temperature sensor channel Svyatoslav Ryhel
2025-04-05 15:23 ` Svyatoslav Ryhel
2025-04-12 10:53 ` Jonathan Cameron
2025-04-12 11:06 ` Svyatoslav Ryhel
2025-04-13 9:28 ` Jonathan Cameron
2025-04-13 9:42 ` Svyatoslav Ryhel
2025-04-14 18:35 ` Jonathan Cameron
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=dc772e9e-632f-4c38-a654-833df0800ee1@kernel.org \
--to=krzk@kernel.org \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.com \
/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).