From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC Patch 1/4] mfd: AXP20x: Add power supply bindings documentation
Date: Wed, 5 Nov 2014 15:48:32 +0100 [thread overview]
Message-ID: <20141105144832.GB2989@lukather> (raw)
In-Reply-To: <20141104220827.773c53d0@neptune.home>
On Tue, Nov 04, 2014 at 10:08:27PM +0100, Bruno Pr?mont wrote:
> On Tue, 04 November 2014 Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
> > On Mon, Nov 03, 2014 at 09:02:44PM +0100, Bruno Pr?mont wrote:
> > > Doing something like this?:
> > >
> > > --- a/arch/arm/boot/dts/sun7i-a20-cubietruck.dts
> > > +++ b/arch/arm/boot/dts/sun7i-a20-cubietruck.dts
> > > @@ -126,9 +126,11 @@
> > > interrupt-controller;
> > > #interrupt-cells = <1>;
> > >
> > > - backup = <3000000 200>;
> > > - battery.resistance = <100>;
> > > - battery.capacity = <2000>;
> > > + x-powers,backup = <3000000 200>;
> >
> > I don't really remember what was that property used for. Would it make
> > sense to put it into the battery node?
>
> The backup/rtc battery is completely distinct from main battery.
>
> It's presence is in no way related to that of the main battery,
> thus I would not put it into the same node.
> As all the information needed is included in the property I see
> no reason to move it into a separate node.
Oh. So it is to model some button battery that might be here to keep
the RTC state while the board is unpowered?
How is that related to the PMIC?
Maybe modeling as a fixed regulator would be more accurate.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141105/20fd617b/attachment.sig>
next prev parent reply other threads:[~2014-11-05 14:48 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 [this message]
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
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=20141105144832.GB2989@lukather \
--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