From: Andreas Feuersinger <andreas.feuersinger@spintower.eu>
To: Julien Boibessot <julien.boibessot@free.fr>
Cc: libertas-dev@lists.infradead.org, linux-mmc@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: MX27 libertas_sdio SDIO Interrupts vs available bitrate
Date: Mon, 2 Aug 2010 15:46:05 +0200 [thread overview]
Message-ID: <20100802154605.33a34d59@speedy> (raw)
In-Reply-To: <4C51795F.8000800@free.fr>
Hi Julien!
Julien Boibessot <julien.boibessot@free.fr> wrote:
> Andreas Feuersinger a écrit :
> > Everything works except for very bad datarate. So far the mxc_mmc
> > driver does not handle any SDIO interrupts. Could that be the reason
> > for the bad performance?
> >
> Definitly !
> (I had the same "problem" on my i.MX27 platform before using SDIO
> interrupts)
thank you! At least I know where to go ;)
While trying to enable SDIO handling I look at the mainline kernel
patch for SDIO interrupts in mxcmmc.c.
But in order to apply that I have to port that driver, introduced in
2.6.29 to my 2.6.22 kernel version.
In the first step I try to get it run without sdio support.
The driver seems to load helper firmware successfully and also real
firmware. After that it stops where the libertas driver says:
"waiting for firmware to boot."
Register status is as follows:
mxcmci_irq:status: <6>BUF_WRITE_RDY |<6>END_CMD_RESP |<6>BUF_UND_RUN
|<6>XBUF_EMPTY |<6>YBUF_EMPTY |<6>
Looks like stopped clock? Is the firmware supposed to start some cmd?
I have a different question:
Does anybody know if it is possible to boot freescale development board
mx27pdk using kernel versions greater 2.6.30 ?
thanks
Andreas
next prev parent reply other threads:[~2010-08-02 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 10:46 MX27 libertas_sdio SDIO Interrupts vs available bitrate Andreas Feuersinger
2010-07-29 12:51 ` Julien Boibessot
2010-08-02 13:46 ` Andreas Feuersinger [this message]
2010-07-30 20:08 ` Gabay, Benzy
[not found] ` <676FD6AA0F002F49B89E70F0C5EFD22C1311499C43-f/0pxbFS9PCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2010-08-02 6:40 ` Andreas Feuersinger
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=20100802154605.33a34d59@speedy \
--to=andreas.feuersinger@spintower.eu \
--cc=julien.boibessot@free.fr \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).