From: bonbons@linux-vserver.org (Bruno Prémont)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC Patch 1/4] mfd: AXP20x: Add power supply bindings documentation
Date: Tue, 4 Nov 2014 22:21:24 +0100 [thread overview]
Message-ID: <20141104222124.1bc7e6ec@neptune.home> (raw)
In-Reply-To: <553e634f-ce75-4409-883c-acbfe773e950@googlegroups.com>
Hi Ezaul,
On Tue, 04 November 2014 Ezaul Zillmer <ezaulzillmer@gmail.com> wrote:
> Cubieboard2 + Kernel 3.18-rc3
>
> [ 15.955655] axp20x-regulator axp20x-regulator: regulators node not found
> [ 15.962580] LDO1: 1300 mV
> [ 15.965732] LDO2: at 3000 mV
> [ 15.969120] LDO3: at 2275 mV
> [ 15.972314] LDO4: at 2800 mV
> [ 15.975700] LDO5: at 2800 mV
> [ 15.979075] DCDC2: at 1400 mV
> [ 15.982555] DCDC3: at 1250 mV
> [ 15.985706] axp20x 0-0034: AXP20X driver loaded
>
> What was missing for axp20x work of cubieboard2 dt?
> as poderiar do to run this drive?
Not sure what patches, it at all you have on top of 3.18-rc3.
As far as I know 3.18 should not have any AXP driver that's
not already present in 3.17.
The base AXP driver only includes power-off support and bits for
regulators while the DT part of regulators is missing (at least
for cubietruck).
My patches, ideally combined with Carlo's patches from June or so
I mentioned in introduction mail would include power supply and
input driver for power button. The regulator DT entries are in some
other patch (I think Maxime did have them in some of his trees -
probably defining them causes too much trouble because all uses are
not yet ready to explicitly use them).
On DT side, on top of my patches, for cubieboard2 you might need to
add the backup battery property if it has such a battery - I don't
think the CB2 has a main battery connector but I might be wrong
(I only have a cubietruck).
Except for that a hwmon driver would be useful to cover some of the
last bits of the AXP like temprature sensor and main voltage sensor.
With that about all the features should be covered.
Bruno
next prev parent reply other threads:[~2014-11-04 21:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141020215954.7f1d5502@neptune.home>
2014-10-20 20:33 ` [RFC Patch 1/4] mfd: AXP20x: Add power supply bindings documentation Bruno Prémont
2014-10-21 10:15 ` Lee Jones
2014-10-21 16:09 ` Bruno Prémont
2014-10-21 19:19 ` Maxime Ripard
2014-11-03 20:02 ` Bruno Prémont
2014-11-04 14:31 ` Maxime Ripard
2014-11-04 21:08 ` Bruno Prémont
2014-11-05 14:48 ` Maxime Ripard
2014-11-05 14:55 ` [linux-sunxi] " Koen Kooi
[not found] ` <553e634f-ce75-4409-883c-acbfe773e950@googlegroups.com>
2014-11-04 21:21 ` Bruno Prémont [this message]
2014-10-21 20:10 ` Maxime Ripard
2014-10-20 20:33 ` [RFC Patch 2/4] mfd: AXP20x: Add power supply sub-driver Bruno Prémont
2014-10-21 20:27 ` Maxime Ripard
2014-10-22 6:30 ` Bruno Prémont
2014-10-23 9:29 ` Maxime Ripard
[not found] ` <20141023201235.3b94cc82@smutje.local>
2014-11-03 20:14 ` Bruno Prémont
2014-10-20 20:33 ` [RFC Patch 3/4] mfd: AXP20x: Add power supply defconfig entries Bruno Prémont
2014-10-20 20:33 ` [RFC Patch 4/4] mfd: AXP20x: Add backup battery DTS entry for Cubietruck Bruno Prémont
2014-10-20 20:19 [RFC Patch 0/4] mfd: AXP20x: Add power supply sub-driver Bruno Prémont
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=20141104222124.1bc7e6ec@neptune.home \
--to=bonbons@linux-vserver.org \
--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;
as well as URLs for NNTP newsgroup(s).