From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] sunxi: fix DCDC2 output in CHIP_defconfig
Date: Tue, 8 Mar 2016 23:18:43 +0100 [thread overview]
Message-ID: <20160308221843.GJ8418@lukather> (raw)
In-Reply-To: <20160307155011.2dbc5485@i7>
On Mon, Mar 07, 2016 at 03:50:11PM +0200, Siarhei Siamashka wrote:
> On Mon, 7 Mar 2016 13:44:11 +0100
> Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
>
> > From: Boris Brezillon <boris.brezillon@free-electrons.com>
> >
> > Unlike the datasheet recommendation, the R8 SoC requires a 1.4V supply
> > for its CPU when operating at 1Ghz.
>
> That's interesting. Is this R8 SoC datasheet with the Allwinner
> recommended cpufreq operating points available in public access
> somewhere?
Yeah:
https://github.com/NextThingCo/CHIP-Hardware/tree/master/CHIP%5Bv1_0%5D/CHIPv1_0-BOM-Datasheets
But note that it's the usual datasheet from Allwinner, you don't have
a list of operating points.
> Are they really recommending 1008MHz @1.3V there?
It was a misunderstanding on our side. We thought that the nominal
tension was the recommended one, and our prototypes were running just
fine with it. Later samples (probably from a different batch) turned
out to have memory corruptions because of the lower voltage.
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.denx.de/pipermail/u-boot/attachments/20160308/fbe643ea/attachment.sig>
next prev parent reply other threads:[~2016-03-08 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 12:44 [U-Boot] [PATCH] sunxi: fix DCDC2 output in CHIP_defconfig Maxime Ripard
2016-03-07 13:50 ` Siarhei Siamashka
2016-03-08 22:18 ` Maxime Ripard [this message]
2016-03-16 14:25 ` Hans de Goede
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=20160308221843.GJ8418@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=u-boot@lists.denx.de \
/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