From: Ben Tseng <ben.tseng@mediatek.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Fan Chen <fan.chen@mediatek.com>, Zhang Rui <rui.zhang@intel.com>,
<linux-pm@vger.kernel.org>, <srv_heupstream@mediatek.com>
Cc: Eduardo Valentin <edubezval@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
<hsinyi@chromium.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
Michael Kao <michael.kao@mediatek.com>,
Yu-Chia Chang <ethan.chang@mediatek.com>
Subject: Re: [PATCH v5 2/3] thermal: mediatek: Add LVTS drivers for SoC theraml zones
Date: Fri, 23 Jul 2021 14:17:25 +0800 [thread overview]
Message-ID: <1f92b245537d6390b7b2bde62ce8b99a3df9d445.camel@mediatek.com> (raw)
In-Reply-To: <06b1804c-4675-2997-8c5c-bcdffbcfc4a1@linaro.org>
On Mon, 2021-06-21 at 13:26 +0200, Daniel Lezcano wrote:
> On 17/06/2021 13:47, Ben Tseng wrote:
> > From: Michael Kao <michael.kao@mediatek.com>
> >
> > Add a LVTS (Low voltage thermal sensor) driver to report junction
> > temperatures in Mediatek SoC and register the maximum temperature
> > of sensors and each sensor as a thermal zone.
>
> I think we already talked about that. We don't want a thermal sensor
> driver to aggregate the temperatures but create some kindof virtual
> sensor with a property (min, max, avg, ...) which is usable by
> anyone.
>
> [ ... ]
>
>
>
Dear Daniel,
Sorry for the late reply.
After survey ,I'm not sure whether the patch[1] is the architecture of
virtual thermal sensor which you commented.
Or, is there any existing framework on mainline already support virtual
sensor?
Could you help to provide reference to us?
Thank you so much.
[1]
https://patchwork.kernel.org/project/linux-pm/patch/1606466204-31657-1-git-send-email-gao.yunxiao6@gmail.com/
BRs
Ben
next prev parent reply other threads:[~2021-07-23 6:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 11:47 [PATCH v5 0/3] thermal: mediatek: Add LVTS architecture thermal controller Ben Tseng
2021-06-17 11:47 ` [PATCH v5 1/3] thermal: mediatek: Relocate driver to mediatek folder Ben Tseng
2021-06-18 13:56 ` Matthias Brugger
2021-06-17 11:47 ` [PATCH v5 2/3] thermal: mediatek: Add LVTS drivers for SoC theraml zones Ben Tseng
2021-06-21 11:26 ` Daniel Lezcano
2021-07-23 6:17 ` Ben Tseng [this message]
2021-08-16 18:56 ` Daniel Lezcano
2022-04-05 10:53 ` AngeloGioacchino Del Regno
2021-06-17 11:47 ` [PATCH v5 3/3] dt-bindings: thermal: Add binding document for mt6873 thermal controller Ben Tseng
2021-06-18 19:10 ` Rob Herring
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=1f92b245537d6390b7b2bde62ce8b99a3df9d445.camel@mediatek.com \
--to=ben.tseng@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=ethan.chang@mediatek.com \
--cc=fan.chen@mediatek.com \
--cc=hsinyi@chromium.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=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=michael.kao@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=srv_heupstream@mediatek.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).