From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Francesco Dolcini <francesco.dolcini@toradex.com>,
Marco Felsch <m.felsch@pengutronix.de>
Cc: l.stach@pengutronix.de, linux-pm@vger.kernel.org,
"Rafael J . Wysocki" <rafael@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Amit Kucheria <amitk@kernel.org>,
Jon Nettleton <jon@solid-run.com>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Tim Harvey <tharvey@gateworks.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1] thermal: imx: Make trip point offset configurable
Date: Tue, 24 May 2022 15:17:24 +0200 [thread overview]
Message-ID: <4ba1d7d2-3e8c-ba60-37fd-9598f415c076@linaro.org> (raw)
In-Reply-To: <20220524100728.GA99192@francesco-nb.int.toradex.com>
Hi Francesco,
On 24/05/2022 12:07, Francesco Dolcini wrote:
> On Tue, May 24, 2022 at 10:35:14AM +0200, Marco Felsch wrote:
>> On 22-05-23, Francesco Dolcini wrote:
>>> On Wed, May 18, 2022 at 12:10:34PM +0200, Daniel Lezcano wrote:
>>>> It would have been easier if the imx6/7 platforms were defining the thermal
>>>> zones in their DT ...
>>
>> After checking the driver I completely agree with you... But this would
>> need much more rework.
>>
>>> Marco, Lucas,
>>> What about a &tempon { fsl,tempmon-critical-offset=<0>; } dt property?
>>
>> I would not introduce a special binding for it. Instead I would add the
>> support to parse the already exisiting bindings so the new-tempmon node
>> would look like:
>>
>> tempmon: tempmon {
>> compatible = "fsl,imx6q-tempmon";
>> interrupt-parent = <&gpc>;
>> interrupts = <0 49 IRQ_TYPE_LEVEL_HIGH>;
>> fsl,tempmon = <&anatop>;
>> nvmem-cells = <&tempmon_calib>, <&tempmon_temp_grade>;
>> nvmem-cell-names = "calib", "temp_grade";
>> clocks = <&clks IMX6QDL_CLK_PLL3_USB_OTG>;
>> #thermal-sensor-cells = <0>;
>>
>> commercial-thermal {
>> trips {
>> commercial_trip_passive: trip-point0 {
>> temperature = <85000>;
>> type = "passive";
>> };
>> commercial_trip_crit: trip-point1 {
>> temperature = <90000>;
>> type = "critical";
>> };
>> };
>> };
>>
>> extended-commercial-thermal {
>> trips {
>> ecommercial_trip_passive: trip-point0 {
>> temperature = <95000>;
>> type = "passive";
>> };
>> ecommercial_trip_crit: trip-point1 {
>> temperature = <100000>;
>> type = "critical";
>> };
>> };
>> };
>>
>> industrial-thermal { };
>> automotive-thermal { };
>> };
>>
>> That way we can reuse the existing dt definitions and if no *-thermal
>> child device nodes exist we can keep the original logic.
>
> Good for me, it's more work, of course, but if this is the way to do it
> let it be.
> Daniel: I'd like to have an ack from you before implementing this.
It sounds like a correct approach, especially that is back compatible
with old DTs.
--
<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
prev parent reply other threads:[~2022-05-24 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 19:00 [PATCH v1] thermal: imx: Make trip point offset configurable Francesco Dolcini
2022-05-16 19:06 ` Ahmad Fatoum
2022-05-16 19:16 ` Francesco Dolcini
2022-05-17 4:36 ` Ahmad Fatoum
2022-05-17 15:29 ` Francesco Dolcini
2022-05-18 8:55 ` Marco Felsch
2022-05-18 9:49 ` Francesco Dolcini
2022-05-18 10:10 ` Daniel Lezcano
2022-05-23 14:35 ` Francesco Dolcini
2022-05-24 8:35 ` Marco Felsch
2022-05-24 10:07 ` Francesco Dolcini
2022-05-24 13:17 ` Daniel Lezcano [this message]
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=4ba1d7d2-3e8c-ba60-37fd-9598f415c076@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=amitk@kernel.org \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=jon@solid-run.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-pm@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=rafael@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tharvey@gateworks.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