From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Icenowy Zheng <icenowy@aosc.xyz>
Cc: rui.zhang@intel.com, edubezval@gmail.com, robh+dt@kernel.org,
wens@csie.org, emilio@elopez.com.ar, mark.rutland@arm.com,
linux@armlinux.org.uk, mturquette@baylibre.com,
sboyd@codeaurora.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [RFC PATCH 3/5] thermal: Add support for the thermal sensor on A23/33
Date: Tue, 28 Jun 2016 13:46:40 +0200 [thread overview]
Message-ID: <20160628114640.GE5550@lukather> (raw)
In-Reply-To: <20160628101325.2522-3-icenowy@aosc.xyz>
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
Hi,
Thanks for working on this.
On Tue, Jun 28, 2016 at 06:13:23PM +0800, Icenowy Zheng wrote:
> This patch adds support for the sun8iw3 thermal sensor on
> Allwinner A23/33 SoCs.
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.xyz>
The IP is awfully similar to the A31's, which already has a driver
(drivers/input/touchscreen/sun4i-ts.c).
There's no reason to add a new one here.
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2016-06-28 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160628101325.2522-1-icenowy@aosc.xyz>
[not found] ` <20160628101325.2522-3-icenowy@aosc.xyz>
2016-06-28 11:46 ` Maxime Ripard [this message]
[not found] ` <60021467122182@web19j.yandex.ru>
2016-06-29 12:10 ` [RFC PATCH 3/5] thermal: Add support for the thermal sensor on A23/33 Maxime Ripard
[not found] ` <1112501467207099@web30g.yandex.ru>
2016-06-29 13:42 ` Maxime Ripard
2016-07-05 6:12 ` [RFC PATCH 1/5] clk: sunxi: Add a driver for the PLL2 on A31/23/33 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=20160628114640.GE5550@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=emilio@elopez.com.ar \
--cc=icenowy@aosc.xyz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=sboyd@codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).