From: Roberto Nibali <rnibali@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: SD card probe failure
Date: Wed, 23 May 2012 10:54:22 +0200 [thread overview]
Message-ID: <CAONxwYNpAcNS_UQSSAq+FuJsw0g89YRD6DO-3c9nEs-L7Ap4pQ@mail.gmail.com> (raw)
In-Reply-To: <20120523083809.GU30400@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1757 bytes --]
Hi
> What's going on here? I'll investigate this further, because in real life
> I
> > have massive SD card write speed issues on my mx25 device on any kernel
> > tested from 2.6.37 to 3.3.4 so far.
>
> I try to keep the iomux descriptions in sync with the kernel. So when
> there is a bug in the kernel it's likely present in barebox aswell.
> Another thing which you might want to investigate is the clock
> frequency. Please check with an oscilloscope if we really have 25MHz as
> suggested above.
>
>
I used exactly the same iomux descriptions, but we have the same issue in
the kernel with huge timeouts. One of the reasons I try to switch to
barebox is its simplicity of the driver ideology close to the kernel. Also,
what are the default pin mux settings for the ESDHC on mx25, if I comment
the following?
/*
MX25_PAD_SD1_CMD__SD1_CMD,
MX25_PAD_SD1_CLK__SD1_CLK,
MX25_PAD_SD1_DATA0__SD1_DATA0,
MX25_PAD_SD1_DATA1__SD1_DATA1,
MX25_PAD_SD1_DATA2__SD1_DATA2,
MX25_PAD_SD1_DATA3__SD1_DATA3,
*/
I thought it might just fallback to the same pin mux but without the 47k
pullup (NO_PAD_CTRL). This does not seem to be the case, because I have
replaced the definition of the iomux definitions with NO_PAD_CTRL and the
problem remains. Only commenting them out seems to have an effect. So,
something is either really wrong with my hardware or there has to be
another influence.
The oscilloscope shows 190kHz when it fails, 33.33MHz when it works ....
interesting. Barebox initializes mpll to 532Mhz and consequently sets sdhc1
to 66.5Mzh. Invoking 'cpufreq 399' resets the clocks, however does not
adjust the sdhc1 one as on the oscilloscope it stays on 33.33Mhz.
What next?
Cheers
Roberto
[-- Attachment #1.2: Type: text/html, Size: 2294 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-05-23 8:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 14:28 Roberto Nibali
2012-05-22 18:48 ` Sascha Hauer
2012-05-22 19:01 ` Eric Bénard
2012-05-23 8:30 ` Roberto Nibali
2012-05-23 8:38 ` Sascha Hauer
2012-05-23 8:54 ` Roberto Nibali [this message]
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=CAONxwYNpAcNS_UQSSAq+FuJsw0g89YRD6DO-3c9nEs-L7Ap4pQ@mail.gmail.com \
--to=rnibali@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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