From: Pascal PAILLET-LME <p.paillet@st.com>
To: "rui.zhang@intel.com" <rui.zhang@intel.com>,
"edubezval@gmail.com" <edubezval@gmail.com>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"amit.kucheria@verdurent.com" <amit.kucheria@verdurent.com>,
"mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
David HERNANDEZ SANCHEZ <david.hernandezsanchez@st.com>,
"horms+renesas@verge.net.au" <horms+renesas@verge.net.au>,
"wsa+renesas@sang-engineering.com"
<wsa+renesas@sang-engineering.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH_V3 0/6] thermal: stm32: driver improvements
Date: Mon, 27 Jan 2020 13:17:50 +0000 [thread overview]
Message-ID: <a400d4e2-4abb-aad8-73f0-57c9300ca351@st.com> (raw)
In-Reply-To: <20200110101605.24984-1-p.paillet@st.com>
The goal of this patchset is to improve and simplify the stm32 thermal
> driver:
> * let the framework handle the trip points: it very is hard to split this patch
> into smaller ones and keep each individual patch functional.
> * fix interrupt management to avoid receiving hundreds of
> interrupts when the temperature is close to the low threshold.
> * improve temperature reading resolution
> * the dirver is backawrd compatible.
>
> Pascal Paillet (6):
> changes in v2:
> * Split "handle multiple trip points" patch to make ones:
> * rework sensor mode management
> * disable interrupts at probe
> * "remove hardware irq handler" is squashed in "handle multiple trip points"
kind reminder for review
> thermal: stm32: fix icifr register name
> thermal: stm32: rework sensor mode management
> thermal: stm32: disable interrupts at probe
> thermal: stm32: handle multiple trip points
> thermal: stm32: improve temperature computing
> thermal: stm32: fix low threshold interrupt flood
>
> drivers/thermal/st/stm_thermal.c | 388 ++++++++++---------------------
> 1 file changed, 120 insertions(+), 268 deletions(-)
>
next prev parent reply other threads:[~2020-01-27 13:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 10:15 [PATCH_V3 0/6] thermal: stm32: driver improvements Pascal Paillet
2020-01-10 10:16 ` [PATCH_V3 1/6] thermal: stm32: fix icifr register name Pascal Paillet
2020-01-10 10:16 ` [PATCH_V3 2/6] thermal: stm32: rework sensor mode management Pascal Paillet
2020-01-10 10:16 ` [PATCH_V3 3/6] thermal: stm32: disable interrupts at probe Pascal Paillet
2020-01-10 10:16 ` [PATCH_V3 4/6] thermal: stm32: handle multiple trip points Pascal Paillet
2020-01-10 10:16 ` [PATCH_V3 5/6] thermal: stm32: improve temperature computing Pascal Paillet
2020-01-10 10:16 ` [PATCH_V3 6/6] thermal: stm32: fix low threshold interrupt flood Pascal Paillet
2020-01-27 13:17 ` Pascal PAILLET-LME [this message]
2020-01-27 14:39 ` [PATCH_V3 0/6] thermal: stm32: driver improvements 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=a400d4e2-4abb-aad8-73f0-57c9300ca351@st.com \
--to=p.paillet@st.com \
--cc=alexandre.torgue@st.com \
--cc=amit.kucheria@verdurent.com \
--cc=daniel.lezcano@linaro.org \
--cc=david.hernandezsanchez@st.com \
--cc=edubezval@gmail.com \
--cc=horms+renesas@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=rui.zhang@intel.com \
--cc=wsa+renesas@sang-engineering.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).