From: edubezval@gmail.com (Eduardo Valentin)
To: linux-arm-kernel@lists.infradead.org
Subject: Freescale IMX6 active cooling
Date: Wed, 18 Nov 2015 13:56:55 -0800 [thread overview]
Message-ID: <20151118215654.GA23251@localhost.localdomain> (raw)
In-Reply-To: <CABH3fy-UY7YdbaaZxymfcaxnhsNkozeRD9uUU5DOQH2S50sEXQ@mail.gmail.com>
Hello,
On Wed, Nov 18, 2015 at 12:00:05PM +0200, Catalin Crenguta wrote:
> On Wed, Nov 18, 2015 at 6:53 AM, Sean Cross <xobs@kosagi.com> wrote:
> > Perhaps the correct order of patches is:
> >
> > 1) Add generic thermal zone support
> > 2) Remove zone and cdev from imx_thermal
> > 3) Add cpufreq-cooling to imx6
> > 4) Add cpufreq-cooling to all other SoCs that support imx_thermal
> > 5) Add default generic thermal zone support to imx6qdl.dtsi
> In my opinion, I guess a patch series containing this would be good.
The recommendation is for you to use of-thermal, yes. In that way you
may benefit of describing your thermal hw specific data over DT. And you
can benefit of the existing cooling devices that have DT cooling
descriptors too, such as gpio-fan, and cpufreq-cooling, yes.
To use cpufreq-cooling, you may want to make sure your device works with
cpufreq-dt driver.
I would appreciate if you could clean up the IMX code to use the DT way
of describing thermal.
BR,
>
> Thanks again!
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-11-18 21:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 9:43 Freescale IMX6 active cooling Catalin Crenguta
2015-11-16 14:51 ` Fabio Estevam
2015-11-17 9:38 ` Jon Nettleton
2015-11-17 12:49 ` Catalin Crenguta
2015-11-18 4:53 ` Sean Cross
2015-11-18 10:00 ` Catalin Crenguta
2015-11-18 21:56 ` Eduardo Valentin [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=20151118215654.GA23251@localhost.localdomain \
--to=edubezval@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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