linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ondřej Jirman" <megous@megous.com>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Ziping Chen <techping.chan@gmail.com>,
	wens@csie.org, robh@kernel.org, mark.rutland@arm.com,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com
Subject: Re: [linux-sunxi] Re: [PATCH v3 1/3] input: sun4i-a10-lradc-keys: Add support for A83T
Date: Tue, 26 Mar 2019 21:26:34 +0100	[thread overview]
Message-ID: <20190326202634.di2rhacp2izeqyg3@core.my.home> (raw)
In-Reply-To: <20170626171342.pdr7xdiaki4i5bdt@flea.lan>

Hello,

On Mon, Jun 26, 2017 at 07:13:42PM +0200, Maxime Ripard wrote:
> On Sat, Jun 24, 2017 at 10:45:13AM +0800, Ziping Chen wrote:
> > From: Ziping Chen <techping.chan@gmail.com>
> > 
> > Allwinner A83T SoC has a low res adc like the one
> > in Allwinner A10 SoC, however, the A10 SoC's vref
> > of lradc internally is divided by 2/3 and the A83T
> > SoC's vref of lradc internally is divided by 3/4,
> > thus add a hardware variant for it to be compatible
> > with various devices.
> > 
> > Signed-off-by: Ziping Chen <techping.chan@gmail.com>
> 
> Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>

Can we move on with this patch series? It's a few years and it doesn't seem that
there is any interest/progress with lradc iio based driver, and merging this
wouldn't block that effort anyway (as suggested in other replies).

I can re-send the series with the changed compatible name, and add a mainline
user of this driver (A83T based TBS-A711 tablet).

Any objections?

regards,
	o.

> Thanks!
> Maxime
> 
> -- 
> Maxime Ripard, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
> 
> -- 
> You received this message because you are subscribed to the Google Groups "linux-sunxi" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



  reply	other threads:[~2019-03-26 20:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-24  2:45 [PATCH v3 0/3] Allwinner A83T R_LRADC support Ziping Chen
2017-06-24  2:45 ` [PATCH v3 1/3] input: sun4i-a10-lradc-keys: Add support for A83T Ziping Chen
2017-06-26 17:13   ` Maxime Ripard
2019-03-26 20:26     ` Ondřej Jirman [this message]
2017-06-24  2:45 ` [PATCH v3 2/3] dt-bindings: input: Add R_LRADC " Ziping Chen
2017-06-26 17:15   ` Maxime Ripard
2017-06-27 15:18     ` Ziping Chen
2017-06-27 15:29       ` [linux-sunxi] " icenowy
2017-06-27 17:36         ` Maxime Ripard
2017-06-27 18:15           ` Alexandre Belloni
2017-06-29  4:45           ` Ziping Chen
2017-06-29  7:53             ` Maxime Ripard
2017-06-29 12:19               ` Ziping Chen
2017-06-27 17:31       ` Maxime Ripard
2017-06-29  4:35         ` Ziping Chen
2017-06-29  7:52           ` Maxime Ripard
2017-06-24  2:45 ` [PATCH v3 3/3] ARM: dts: sunxi: " Ziping Chen

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=20190326202634.di2rhacp2izeqyg3@core.my.home \
    --to=megous@megous.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=mark.rutland@arm.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=robh@kernel.org \
    --cc=techping.chan@gmail.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;
as well as URLs for NNTP newsgroup(s).