From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] About the thermal sensor driver on H3/A64/H5
Date: Wed, 29 Mar 2017 14:29:58 +0200 [thread overview]
Message-ID: <20170329122958.54mgggxnztsctblg@lukather> (raw)
In-Reply-To: <20170328191855.69809125838@relay.mailchannels.net>
On Wed, Mar 29, 2017 at 03:18:43AM +0800, Icenowy Zheng wrote:
>
> 2017?3?29? ??3:14? Vincent Legoll <vincent.legoll@gmail.com>???
> >
> > Hello,
> >
> > On Tue, Mar 28, 2017 at 6:40 PM, Icenowy Zheng <icenowy@aosc.io> wrote:
> > > I'm trying to do a mainlinable thermal driver for H3/A64/H5 SoCs;
> >
> > What's the relationship with:
> > - DVFS - from Ond?ej Jirman
> > - THS - from Josef Gajdusek
> >
> > See : http://linux-sunxi.org/Linux_mainlining_effort#Minor_drivers
> >
> > Are those not suitable ? unrelated ?
>
> The second one is reject by Maxime.
>
> The DVFS will come in after thermal is proper.
Not really, we can totally do DVFS without thermal support. What we
can't do is thermal throttling, which is related, but not a hard
dependency.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170329/51e1d2ee/attachment-0001.sig>
next parent reply other threads:[~2017-03-29 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170328191855.69809125838@relay.mailchannels.net>
2017-03-29 12:29 ` Maxime Ripard [this message]
2017-03-28 16:40 About the thermal sensor driver on H3/A64/H5 Icenowy Zheng
2017-03-28 19:14 ` [linux-sunxi] " Vincent Legoll
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=20170329122958.54mgggxnztsctblg@lukather \
--to=maxime.ripard@free-electrons.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