From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Icenowy Zheng <icenowy@aosc.xyz>
Cc: Zhang Rui <rui.zhang@intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Ondrej Jirman <megous@megous.com>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] thermal: add support for the thermal sensor on Allwinner new SoCs
Date: Tue, 28 Feb 2017 07:44:26 +0100 [thread overview]
Message-ID: <20170228064426.jsukm53ybaatpgyx@lukather> (raw)
In-Reply-To: <20170227194054.51951-2-icenowy@aosc.xyz>
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
On Tue, Feb 28, 2017 at 03:40:53AM +0800, Icenowy Zheng wrote:
> From: Ondrej Jirman <megous@megous.com>
>
> Allwinner SoCs from H3 (including H5, A64, etc) have a new version of
> thermal sensor, and needs a new driver for it.
>
> Add such a driver.
>
> Currently only H3 is supported, but other SoCs are easily to be
> supported by adding new formula and set the sensor number.
>
> Signed-off-by: Ondřej Jirman <megous@megous.com>
> [Icenowy: extend to support further multiple-sensor SoCs, change commit
> message]
> Signed-off-by: Icenowy Zheng <icenowy@aosc.xyz>
There's no need to create a new driver for that. This can be handled
by the GPADC driver we already have.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next parent reply other threads:[~2017-02-28 6:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170227194054.51951-1-icenowy@aosc.xyz>
[not found] ` <20170227194054.51951-2-icenowy@aosc.xyz>
2017-02-28 6:44 ` Maxime Ripard [this message]
[not found] <20170301054835.mUDm4hZv@smtp2m.mail.yandex.net>
2017-03-01 10:14 ` Maxime Ripard
[not found] <20170301132108.L3LK6WWv@smtp1h.mail.yandex.net>
2017-03-01 15:56 ` Maxime Ripard
[not found] <20170301190220.2EgSha6N@smtp3o.mail.yandex.net>
2017-03-02 14:11 ` Maxime Ripard
[not found] ` <8250311489019784@web18g.yandex.ru>
2017-03-09 14:27 ` Maxime Ripard
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=20170228064426.jsukm53ybaatpgyx@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=icenowy@aosc.xyz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=megous@megous.com \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=wens@csie.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®