ADDENDUM:
I tried to increase max_blk_count and it breaks after a few tests.
I will redo your tests in a jiffy, however the latency issues worry
me a wee bit.
Increasing max_blk_count did not help really, however I am not sure if
setting it unconditionally to 65535 was the only change I
Anybody with more insights? Why is the interval between two CMD24
more or less in the range of 6ms and the CMD13 follows in varying
intervals between 1ms to 4ms? What's keeping the driver from bursting
CMD24 and successive CMD13 requests?
A 4*128KB dd run shows the following patterns of latency
G'day
This is still present, and we have absolutely no idea where to continue
searching for the solution of the problem. Any pointers? Any git trees
of mmc driver changes we could try? Anybody else with a MX25 that has
this issue?
Hi:
-110 is the timeout problem.
You can dump the esdhc
ADDENDUM:
On Tue, 27 Mar 2012 09:32:36 +0200, joancarles wrote:
G'day
This is still present, and we have absolutely no idea where to
continue searching for the solution of the problem. Any pointers? Any
git trees of mmc driver changes we could try? Anybody else with a
MX25
that has
Hi Eric
G'day
This is still present, and we have absolutely no idea where to
continue
searching for the solution of the problem. Any pointers? Any git
trees
of mmc driver changes we could try? Anybody else with a MX25 that
has
this issue?
does that attached patch fix your problem ?
Hi
Interesting question is now why it worked on your older kernel? The
code
around BROKEN_TIMEOUT is there for much longer, I'd think.
not in fact it seems to have been broken from a long time and I think
I'm responsible of that in 37865fe91582582a6f6c00652f6a2b1ff71f8a78
mmc:
Hi
Might be unrelated, however I have been keeping my eyes on the fix
of
ENGcm07207 quirk introduced with 16a790bcc. According to the
IMX25CE.pdf, to abort data transfers on the AHB, software can reset
the
eSDHC by writing 1 to SYSCTL[24] (RSTA), which currently is not done
with
Hi
Thank you for your reply. I has taken me a while to figure out what you
meant, but I believe I have added a sdhci_dumpregs(host) to the place
where CMD24 is issued with a -110 return error.
Hi:
-110 is the timeout problem.
You can dump the esdhc registers if you want to debug into this
I'd recommend:
git log v2.6.39.. drivers/mmc/host/sdhci-esdhc-imx.c
I have been staring at those commits, however with very little
domain knowledge it's a shot in the dark.
Have you tried copying sdhci-esdhc-imx.c from 2.6.39 to the current
kernel
(might need some build fixes)? If that
Hi
On Tue, 06 Mar 2012 11:29:50 +, joancarles wrote:
Hi
I have the following error when trying to access the SD-card on my
MX25
device:
root@mx25-noah:~$ mount /media/card/
root@mx25-noah:~$ df -kh /media/card
FilesystemSize Used Available Use% Mounted on
/dev
Hi
On Mon, 12 Mar 2012 14:24:23 +0100, Wolfram Sang wrote:
What could have changed between 2.6.39.3 and 3.3-rc5 to trigger this
behaviour? A quick look at
git diff v2.6.39 drivers/mmc/host/sdhci-esdhc-imx.c
I'd recommend:
git log v2.6.39.. drivers/mmc/host/sdhci-esdhc-imx.c
I have been
Hi
I have the following error when trying to access the SD-card on my MX25
device:
root@mx25-noah:~$ mount /media/card/
root@mx25-noah:~$ df -kh /media/card
FilesystemSize Used Available Use% Mounted on
/dev/mmcblk0p1 123.6M 2.7M120.9M 2% /media/card
12 matches
Mail list logo
