From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] [RFC] ARM: dts: sunxi: Add regulators and board-specific operating points for LeMaker BananaPi
Date: Tue, 28 Jul 2015 14:55:45 +0200 [thread overview]
Message-ID: <20150728125545.GC2564@lukather> (raw)
In-Reply-To: <20150728090216.892076C80D94@dd34104.kasserver.com>
On Tue, Jul 28, 2015 at 11:02:16AM +0200, Timo Sigurdsson wrote:
> Hi,
>
> Chen-Yu Tsai schrieb am 27.07.2015 15:14:
> >> ChenYu (in the CC), since you did most of the original work here, do
> >> you know why we have an op at 0.9 volt, but none of our boards allow the
> >> voltage to go that low in the regulator settings ?
> >
> > I'm on vacation now, so apologies for the bad formatting.
> >
> > The OPPs are from a common subset
> > of the settings from the fex files available
> > at the time. Some fex files actually set
> > min and max voltage thus eliminating
> > the highest and lowest OPPs.
> >
> > At least that is how Maxime and I
> > interpreted them.
>
> IMHO for a common maximum opp that's a good approach. But for the lowest
> frequency setting, it would seem more logical to me, to raise the voltage
> to a point where all boards will run fine with them, unless those boards
> cannot handle the frequency regardless of the higher voltage.
Agreed.
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/20150728/5a5e33c7/attachment-0001.sig>
next prev parent reply other threads:[~2015-07-28 12:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 1:28 [RFC] ARM: dts: sunxi: Add regulators and board-specific operating points for LeMaker BananaPi Timo Sigurdsson
2015-07-27 8:07 ` [linux-sunxi] " Hans de Goede
2015-07-27 12:09 ` public_timo.s at silentcreek.de
2015-07-27 12:43 ` Hans de Goede
2015-07-28 9:02 ` Timo Sigurdsson
2015-07-28 12:55 ` Maxime Ripard
2015-07-28 14:57 ` Timo Sigurdsson
2015-07-28 12:49 ` Maxime Ripard
2015-07-28 14:24 ` Hans de Goede
2015-07-28 15:09 ` Timo Sigurdsson
2015-07-28 15:29 ` Hans de Goede
2015-08-02 22:00 ` Timo Sigurdsson
2015-07-28 14:45 ` Timo Sigurdsson
2015-07-27 12:36 ` public_timo.s at silentcreek.de
2015-07-27 12:54 ` Hans de Goede
[not found] ` <CAGb2v65ApKvrj6K+kw43u=0q6=auTsmQjCXhibgZkW+vd5nDqA@mail.gmail.com>
2015-07-28 9:02 ` Timo Sigurdsson
2015-07-28 12:55 ` Maxime Ripard [this message]
2015-07-28 15:01 ` Timo Sigurdsson
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=20150728125545.GC2564@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