From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] arm: sunxi: Add AXP20X_ADC
Date: Mon, 24 Jul 2017 10:18:46 +0200 [thread overview]
Message-ID: <20170724081846.b2rokuwhyuymj3sj@flea> (raw)
In-Reply-To: <CAGb2v64tx6M1CJSKr_wgD4LM+-ER+Yqpj-hUftptj41PVhbBBA@mail.gmail.com>
Hi,
On Sat, Jul 22, 2017 at 10:19:08AM +0800, Chen-Yu Tsai wrote:
> On Sat, Jul 22, 2017 at 12:20 AM, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
> > The APX20X_POWER option, that is a dependency of the USB controllers
> > depends on IIO and AXP20X_ADC. Add it so that we can get a working USB
> > back.
>
> The statement is only half true. AXP20X_POWER can fall back to reading
> the ADC registers directly if AXP20X_ADC is not enabled. Is there a plan
> to remove this feature?
I never really considered this a feature, but some compatibility for
older DTs to be honest :)
> Also, AXP20X_ADC is only really needed if the hardware is AXP20x, and
> not the later ones that don't have voltage/current sensing. I would
> like to change the hard dependency on AXP20X_ADC to the "imply"
> keyword in Kconfig for the AC and battery power supply drivers.
I'm not sure. It's also needed when you want to read the battery
voltage and current, or the AC-IN voltage. And that's a feature found
on all PMICs.
And since the battery and the AC-IN power supplies also have a
dependency on AXP20X_ADC, I guess we can just add a depnds on. In most
configuration, it's going to be enabled anyway.
> That is another discussion though.
Indeed.
> So I think the description should be something like
>
> AXP20X_POWER depends on IIO. Even though it does not depend on
> AXP20X_ADC, it is the new, preferred way of getting power supply
> readings. The other AXP power supply drivers use it as well.
>
> Enable both options.
That works for me.
With that comment, do I have your Acked-By?
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/20170724/bed2243b/attachment.sig>
next prev parent reply other threads:[~2017-07-24 8:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 16:20 [PATCH 1/4] arm: multi_v7: Add AXP20X_POWER Maxime Ripard
2017-07-21 16:20 ` [PATCH 2/4] arm: sunxi: refresh the defconfig Maxime Ripard
2017-07-22 2:05 ` Chen-Yu Tsai
2017-07-24 8:12 ` Maxime Ripard
2017-07-21 16:20 ` [PATCH 3/4] arm: sunxi: Add AXP20X_ADC Maxime Ripard
2017-07-22 2:19 ` Chen-Yu Tsai
2017-07-24 6:43 ` Quentin Schulz
2017-07-24 7:48 ` Chen-Yu Tsai
2017-07-24 8:10 ` Maxime Ripard
2017-07-24 8:41 ` Quentin Schulz
2017-07-24 9:33 ` Maxime Ripard
2017-07-24 8:18 ` Maxime Ripard [this message]
2017-07-24 8:22 ` Chen-Yu Tsai
2017-07-24 9:44 ` Maxime Ripard
2017-07-24 8:47 ` Quentin Schulz
2017-07-21 16:20 ` [PATCH 4/4] arm: sunxi: Add additional power supplies Maxime Ripard
2017-07-22 2:20 ` Chen-Yu Tsai
2017-07-24 8:13 ` Maxime Ripard
2017-07-24 8:14 ` [PATCH 1/4] arm: multi_v7: Add AXP20X_POWER Chen-Yu Tsai
2017-07-25 14:30 ` 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=20170724081846.b2rokuwhyuymj3sj@flea \
--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