From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: bchihi@baylibre.com, angelogioacchino.delregno@collabora.com,
rafael@kernel.org, amitk@kernel.org, rui.zhang@intel.com,
matthias.bgg@gmail.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, rdunlap@infradead.org,
ye.xingchen@zte.com.cn, p.zabel@pengutronix.de
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
khilman@baylibre.com, james.lo@mediatek.com,
rex-bc.chen@mediatek.com
Subject: Re: [PATCH v14 0/6] Add LVTS Thermal Architecture
Date: Fri, 10 Feb 2023 07:44:56 +0100 [thread overview]
Message-ID: <b41930f9-89d9-1b12-b024-05fb12700769@linaro.org> (raw)
In-Reply-To: <20230209105628.50294-1-bchihi@baylibre.com>
On 09/02/2023 11:56, bchihi@baylibre.com wrote:
> From: Balsam CHIHI <bchihi@baylibre.com>
>
> The LVTS (Low Voltage Thermal Sensor) driver is capable of monitoring
> multiple hot points. For that, it contains 7 thermal control blocks
> dedicated to specific devices on the die. Each control block can handle
> up to 4 sensors.
>
> The thermal controller supports several interrupts. One for the cold
> trip point, the hot trip point, the return to the normal trip point,
> and a specific programmable trip point to monitor the temperature
> dynamically.
>
> The temperature measurement can be done in two ways, the immediate mode
> where the temperature read is instantaneous and the filtered mode where
> the controller uses, by configuration, an average of a set of values
> removing the minimum and the maximum.
>
> Finally, it is composed of 2 finite-state machines responsible for
> the state of the temperature (cold, hot, hot 2 normal, hot hot),
> the triggering of the interrupts, and the monitoring of the temperature.
>
> As requested, the thermal driver has been reworked to reduce
> the complexity of the code. At this time, the 4 little CPUs and
> the 4 big CPUs are supported by the thermal driver.They are described
> in a data structure and more devices can be added later.
> The calibration routine has been simplified also.
>
> The series provide the following changes:
> - Move the Mediatek drivers inside a dedicated folder as their number
> is increasing
> - Add the DT bindings for the controller
> - Add the efuse node for the mt8195
> - The LVTS driver
> - The thermal zones description in the DT
Applied patch 1,2 and 4 for v6.3
Patches 5 and 6 should go through the Mediatek tree.
Thanks!
-- Daniel
--
<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:[~2023-02-10 6:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 10:56 [PATCH v14 0/6] Add LVTS Thermal Architecture bchihi
2023-02-09 10:56 ` [PATCH v14 1/6] thermal: drivers: mediatek: Relocate driver to mediatek folder bchihi
2023-02-09 10:56 ` [PATCH v14 2/6] dt-bindings: thermal: mediatek: Add LVTS thermal controllers bchihi
2023-02-09 19:07 ` Rob Herring
2023-02-10 9:09 ` Balsam CHIHI
2023-02-09 10:56 ` [PATCH v14 3/6] arm64: dts: mt8195: Add efuse node to mt8195 bchihi
2023-02-09 16:28 ` Matthias Brugger
2023-02-10 9:08 ` Balsam CHIHI
2023-02-09 10:56 ` [PATCH v14 4/6] thermal: drivers: mediatek: Add the Low Voltage Thermal Sensor driver bchihi
2023-02-09 10:56 ` [PATCH v14 5/6] arm64: dts: mediatek: mt8195: Add thermal zones and thermal nodes bchihi
2023-02-14 14:42 ` Balsam CHIHI
2023-02-09 10:56 ` [PATCH v14 6/6] arm64: dts: mediatek: mt8195: Add temperature mitigation threshold bchihi
2023-02-14 14:43 ` Balsam CHIHI
2023-02-15 12:50 ` AngeloGioacchino Del Regno
2023-02-15 13:13 ` Balsam CHIHI
2023-03-07 11:10 ` Balsam CHIHI
2023-03-31 10:36 ` Matthias Brugger
2023-03-31 11:11 ` Balsam CHIHI
2023-02-10 6:44 ` Daniel Lezcano [this message]
2023-02-10 9:12 ` [PATCH v14 0/6] Add LVTS Thermal Architecture Balsam CHIHI
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=b41930f9-89d9-1b12-b024-05fb12700769@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=amitk@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bchihi@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=james.lo@mediatek.com \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rex-bc.chen@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=ye.xingchen@zte.com.cn \
/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