From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Alice Guo (OSS)" <alice.guo@oss.nxp.com>,
rafael@kernel.org, amitk@kernel.org, rui.zhang@intel.com,
aisheng.dong@nxp.com, shawnguo@kernel.org, leoyang.li@nxp.com
Cc: linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] thermal: Add generic device cooling support
Date: Thu, 5 Jan 2023 10:59:03 +0100 [thread overview]
Message-ID: <0275b025-2029-0a78-1ef8-166bb58d742e@linaro.org> (raw)
In-Reply-To: <20230105082234.16962-2-alice.guo@oss.nxp.com>
On 05/01/2023 09:22, Alice Guo (OSS) wrote:
> From: Anson Huang <Anson.Huang@nxp.com>
>
> To compatible with previous implementation, add generic device
> cooling support, each thermal zone will register a cooling
> device, and when temperature exceed passive trip, the device
> cooling driver will send out a system wide notification, each
> device supporting cooling will need to register device cooling
> and takes action when passive trip is exceeded;
Can you explain the use case you want to solve with this solution and
the limitations of the existing ones ?
--
<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-01-05 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 8:22 [PATCH v1 0/2] add device cooling Alice Guo (OSS)
2023-01-05 8:22 ` [PATCH v1 1/2] thermal: Add generic device cooling support Alice Guo (OSS)
2023-01-05 9:59 ` Daniel Lezcano [this message]
2023-01-05 10:07 ` Alice Guo (OSS)
2023-01-05 8:22 ` [PATCH v1 2/2] thermal: qoriq: Add " Alice Guo (OSS)
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=0275b025-2029-0a78-1ef8-166bb58d742e@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=aisheng.dong@nxp.com \
--cc=alice.guo@oss.nxp.com \
--cc=amitk@kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=shawnguo@kernel.org \
/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®