From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Guenter Roeck <linux@roeck-us.net>, Michael Walle <michael@walle.cc>
Cc: daniel.lezcano@linexp.org, abailon@baylibre.com,
anarsoul@gmail.com, baolin.wang7@gmail.com,
bjorn.andersson@linaro.org, broonie@kernel.org,
damien.lemoal@opensource.wdc.com, digetx@gmail.com,
f.fainelli@gmail.com, glaroque@baylibre.com,
hayashi.kunihiko@socionext.com, heiko@sntech.de,
j-keerthy@ti.com, jonathanh@nvidia.com, khilman@baylibre.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
lukasz.luba@arm.com, matthias.bgg@gmail.com,
mcoquelin.stm32@gmail.com, mhiramat@kernel.org,
miquel.raynal@bootlin.com, niklas.soderlund@ragnatech.se,
rafael@kernel.org, rui.zhang@intel.com, shawnguo@kernel.org,
talel@amazon.com, thierry.reding@gmail.com,
tiny.windzz@gmail.com
Subject: Re: [PATCH v5 00/33] New thermal OF code
Date: Tue, 9 Aug 2022 17:37:17 +0200 [thread overview]
Message-ID: <53d33f48-1774-3a0e-a84e-a8027679ea5a@linaro.org> (raw)
In-Reply-To: <6318d099-268b-1bbe-fed8-4f4b356e90cb@roeck-us.net>
On 09/08/2022 16:32, Guenter Roeck wrote:
> On 8/9/22 01:53, Daniel Lezcano wrote:
>> Hi Guenter,
>>
>> On 08/08/2022 12:26, Guenter Roeck wrote:
>>
>> [ ... ]
>>
>>>> But I guess even if that is fixed, the driver will not probe due to the
>>>> missing trip points? Are they now mandatory? Does it mean we'd need to
>>>> update our device trees? But that will then mean older devices trees
>>>> don't work anymore.
>>>
>>> It would also mean that all hwmon drivers registering a thermal zone
>>> sensor
>>> would fail to register unless such a thermal zone actually exists.
>>
>> Probably missing something but if the thermal zone is not described,
>> the hwmon driver won't initialize. And except if I'm wrong, that was
>> already the case before these changes, no?
>>
>
> In the hwmon source (you point to it below):
>
> if (IS_ERR(tzd)) {
> if (PTR_ERR(tzd) != -ENODEV)
> return PTR_ERR(tzd);
> dev_info(dev, "temp%d_input not attached to any thermal
> zone\n",
> index + 1);
> devm_kfree(dev, tdata);
> return 0;
> }
>
> That contradicts "if the thermal zone is not described, the hwmon driver
> won't initialize".
> Now I must be missing something, since you mention that yourself below,
> and your new patch
> series fixes the problem, at least AFAICS. Confused.
Sorry for not being clear. Let me try to explain it differently.
The function hwmon_thermal_add_sensor() is calling:
Without "[PATCH v5 00/33] New thermal OF code":
-----------------------------------------------
devm_thermal_zone_of_sensor_register(dev, index, ...);
If there is no thermal zone description or the 'dev' does not belong to
any thermal zone then -ENODEV is returned -> OK and the hwmon thermal
zone is _not_ created
With "[PATCH v5 00/33] New thermal OF code":
--------------------------------------------
devm_thermal_of_zone_register(dev, index, ...);
If there is no thermal zone description or the 'dev' does not belong to
any thermal zone then *-EINVAL* is returned -> NOK, error message, and
hwmon thermal zone is _not_ created
With "[PATCH v5 00/33] New thermal OF code" + fixes:
----------------------------------------------------
devm_thermal_of_zone_register(dev, index, ...);
If there is no thermal zone description or the 'dev' does not belong to
any thermal zone then *-ENODEV* is returned -> OK and the hwmon thermal
zone is _not_ created
Quoting your initial message:
"It would also mean that all hwmon drivers registering a thermal zone
sensor would fail to register unless such a thermal zone actually
exists. This would make the whole concept of having the hwmon core
register thermal zone sensors impossible [...]"
The thermal zone must be described if the OF registering function
variant is used. Except I'm wrong that was already the case before the
changes.
Otherwise, nothing prevents a hwmon to register itself with the core
code, that will create the thermal zone.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2022-08-09 15:37 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 22:43 Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 01/33] thermal/of: Rework the thermal device tree initialization Daniel Lezcano
2022-10-18 10:29 ` Ido Schimmel
2022-10-18 10:33 ` Ido Schimmel
2022-10-19 19:53 ` Daniel Lezcano
2022-10-20 10:39 ` Ido Schimmel
2022-08-04 22:43 ` [PATCH v5 02/33] thermal/of: Make new code and old code co-exist Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 03/33] thermal/drivers/rockchip: Switch to new of API Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 04/33] thermal/drivers/uniphier: " Daniel Lezcano
2022-08-15 14:18 ` Kunihiko Hayashi
2022-08-04 22:43 ` [PATCH v5 05/33] thermal/drivers/generic-adc: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 06/33] thermal/drivers/mmio: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 07/33] thermal/drivers/tegra: " Daniel Lezcano
2022-09-06 13:11 ` Dmitry Osipenko
2022-08-04 22:43 ` [PATCH v5 08/33] thermal/drivers/sun8i: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 09/33] thermal/drivers/sprd: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 10/33] thermal/drivers/broadcom: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 11/33] thermal/drivers/qcom: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 12/33] thermal/drivers/st: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 13/33] thermal/drivers/amlogic: " Daniel Lezcano
2022-08-08 8:07 ` Neil Armstrong
2022-08-04 22:43 ` [PATCH v5 14/33] thermal/drivers/armada: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 15/33] thermal/drivers/db8500: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 16/33] thermal/drivers/imx: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 17/33] thermal/drivers/rcar: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 18/33] thermal/drivers/rzg2l: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 19/33] thermal/drivers/qoriq: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 20/33] thermal/drivers/mtk: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 21/33] thermal/drivers/banggap: " Daniel Lezcano
2022-08-04 23:30 ` Bryan Brattlof
2022-08-04 22:43 ` [PATCH v5 22/33] thermal/drivers/maxim: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 23/33] thermal/drivers/hisilicon: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 24/33] thermal/drivers/ti-soc: " Daniel Lezcano
2022-08-05 1:19 ` J, KEERTHY
2022-08-04 22:43 ` [PATCH v5 25/33] ata/drivers/ahci_imx: Switch to new of thermal API Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 26/33] hwmon/drivers/pm_bus: " Daniel Lezcano
2022-08-08 10:29 ` Guenter Roeck
2022-08-10 10:23 ` Daniel Lezcano
2022-08-10 12:41 ` Guenter Roeck
2022-08-04 22:43 ` [PATCH v5 27/33] hwmon/drivers/core: " Daniel Lezcano
2022-08-08 10:27 ` Guenter Roeck
2022-08-04 22:43 ` [PATCH v5 28/33] iio/drivers/sun4i_gpadc: " Daniel Lezcano
2022-08-14 10:11 ` Jernej Škrabec
2022-08-04 22:43 ` [PATCH v5 29/33] Input: sun4i-ts - switch " Daniel Lezcano
2022-08-14 10:12 ` Jernej Škrabec
2022-08-04 22:43 ` [PATCH v5 30/33] regulator/drivers/max8976: Switch " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 31/33] thermal/drivers/samsung: " Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 32/33] thermal/core: Move set_trip_temp ops to the sysfs code Daniel Lezcano
2022-08-04 22:43 ` [PATCH v5 33/33] thermal/of: Remove old OF code Daniel Lezcano
2022-08-08 9:42 ` [PATCH v5 00/33] New thermal " Michael Walle
2022-08-08 10:21 ` Daniel Lezcano
2022-08-08 10:55 ` Michael Walle
2022-08-08 11:06 ` Daniel Lezcano
2022-08-08 10:26 ` Guenter Roeck
2022-08-09 8:53 ` Daniel Lezcano
2022-08-09 14:32 ` Guenter Roeck
2022-08-09 15:37 ` Daniel Lezcano [this message]
2022-08-10 8:34 ` Daniel Lezcano
2022-08-10 9:56 ` Guenter Roeck
2022-08-08 13:09 ` Daniel Lezcano
2022-08-08 13:24 ` Michael Walle
2022-08-08 13:31 ` Daniel Lezcano
2022-08-09 8:23 ` Daniel Lezcano
2022-08-10 8:01 ` Michael Walle
2022-08-10 8:26 ` Daniel Lezcano
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=53d33f48-1774-3a0e-a84e-a8027679ea5a@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=abailon@baylibre.com \
--cc=anarsoul@gmail.com \
--cc=baolin.wang7@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=daniel.lezcano@linexp.org \
--cc=digetx@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=glaroque@baylibre.com \
--cc=hayashi.kunihiko@socionext.com \
--cc=heiko@sntech.de \
--cc=j-keerthy@ti.com \
--cc=jonathanh@nvidia.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lukasz.luba@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mhiramat@kernel.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=niklas.soderlund@ragnatech.se \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=shawnguo@kernel.org \
--cc=talel@amazon.com \
--cc=thierry.reding@gmail.com \
--cc=tiny.windzz@gmail.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
all inboxes | Powered by JetHome®