From: Stanislav Brabec <utx@penguin.cz>
To: Andy Green <andy@warmcat.com>
Cc: Eric Miao <eric.y.miao@gmail.com>,
dbaryshkov@gmail.com, Cyril Hrubis <metan@ucw.cz>,
arminlitzel@web.de, kernel list <linux-kernel@vger.kernel.org>,
Dirk@opfer-online.de, lenz@cs.wisc.edu, rpurdie@rpsys.net,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Pavel Machek <pavel@ucw.cz>,
thommycheck@gmail.com, zaurus-devel@www.linuxtogo.org,
omegamoon@gmail.com
Subject: Re: bit errors on spitz
Date: Fri, 12 Mar 2010 10:07:04 +0100 [thread overview]
Message-ID: <1268384824.4963.35.camel@utx.utx.cz> (raw)
In-Reply-To: <4B995EE1.1050609@warmcat.com>
Andy Green wrote:
> On 03/11/10 15:42, Somebody in the thread at some point said:
> > Andy Green wrote:
> >
> >> I saw very similar failures for a long time on our iMX31 based device.
> >> Eventually I found a Freescale errata where the RAM inside the USB2
> >> macrocell started to make single bit errors below 1.38V Vcore; ours was
> >> 1.4V at that time but dipped on CPU load.
> >
> > Good tip. It seems that nobody ported driver for the voltage control
> > chip ISL6271 from 2.4 kernel, and bootloader probably does not set
> > correct values.
> Unless there's more to it in the way the zaurus using it that regulator
> isn't programmable digitally.
OOPS, I made a mistake and linked ISL6721 instead of ISL6271 there.
Now it is fixed:
http://www.penguin.cz/~utx/zaurus/datasheets/power/XScale/ISL6271A.pdf
This one has I2C. It is connected to GPIO 3 (PWR_SCL) and GPIO 4
(PWR_SDA).
It is visible between the black plastic and the large circular coil:
http://www.penguin.cz/~utx/zaurus/teardown#pcbt
> Reading about your CF Card WLAN related issues they suck down a good
> amount of power when their radio is up, I would definitely suggest
> monitoring with a 'scope the various rails (Vcore, RAM and whatever it
> is the CF Card is powered by) while putting it under load.
I guess that Zaurus has a good power design and that voltage should be
constant enough. CF has a dedicated step down (plus 2.8V power detector
(Why so low, if CF standard requres more?)), HDD has a dedicated step
up/down. USB has dedicated step up. Companion chips use dedicated 3.3V
step down. Audio uses dedicated linear regulator. CPU has several
dedicated step downs, CPU 3.3V uses step-up to 5V and then down to 3.3V
(which is shared only with IOPORT).
Nearest common point between CF card power and CPU power is the battery.
________________________________________________________________________
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus
next prev parent reply other threads:[~2010-03-12 9:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 21:27 Pavel Machek
2010-03-08 5:37 ` Eric Miao
2010-03-08 7:28 ` Pavel Machek
2010-03-08 8:25 ` Cyril Hrubis
2010-03-08 11:48 ` Stanislav Brabec
2010-03-08 12:16 ` Cyril Hrubis
2010-03-08 12:42 ` Russell King - ARM Linux
2010-03-08 13:32 ` Cyril Hrubis
2010-06-03 0:01 ` [URGENT] Re: bit errors on spitz + voipac Marek Vasut
2010-06-03 2:30 ` Eric Miao
2010-03-21 20:40 ` bit errors on spitz Pavel Machek
2010-03-11 13:25 ` Andy Green
2010-03-11 15:42 ` Stanislav Brabec
2010-03-11 21:21 ` Andy Green
2010-03-12 9:07 ` Stanislav Brabec [this message]
2010-03-12 9:33 ` Andy Green
2010-03-12 10:43 ` Stanislav Brabec
2010-03-12 11:13 ` Andy Green
2010-03-21 20:43 ` Pavel Machek
2010-03-21 21:42 ` Stanislav Brabec
2010-03-29 18:27 ` Pavel Machek
2010-03-29 18:52 ` Stanislav Brabec
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=1268384824.4963.35.camel@utx.utx.cz \
--to=utx@penguin.cz \
--cc=Dirk@opfer-online.de \
--cc=andy@warmcat.com \
--cc=arminlitzel@web.de \
--cc=dbaryshkov@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=lenz@cs.wisc.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metan@ucw.cz \
--cc=omegamoon@gmail.com \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=thommycheck@gmail.com \
--cc=zaurus-devel@www.linuxtogo.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
all inboxes | Powered by JetHome®