From: Logan Gunthorpe <logang@deltatee.com>
To: Luciano Coelho <luciano.coelho@nokia.com>
Cc: linux-wireless@vger.kernel.org
Subject: wl1271 with atmel-mci
Date: Thu, 22 Jul 2010 12:33:14 -0600 [thread overview]
Message-ID: <4C488EEA.5020505@deltatee.com> (raw)
Hi Luciano,
I've had the wl1271 working for the most part on an Atmel
micro-controller, but I've been fighting with a bug for the past couple
of days.
The problem happens whenever I try to transmit large packets of data
(using iperf, or nc, etc) the driver would hang and no longer be able to
send packets. tx_queue_len in the debugfs would then grow as I tried to
send packets but nothing would actually be sent to the device. At the
same time receiving packets would consistently work all of the time.
When this occurred I usually got the following messages:
atmel_mci atmel_mci.0: data CRC error
wl1271: ERROR sdio write failed (-84) - addr 0x14fd8, 1076 bytes, 1
(Note: I added the bit at the end of the wl1271 write failed message in
order to try and debug this problem.)
Upon further investigation I found that any calls to sdio_writesb with a
length greater than or equal to 1024 will occasionally fail with a data
CRC error and this would cause the device to stop working.
I have also found that the following ugly hack in wl1271_sdio_raw_write
seems to fix the problem:
if (len <= 1000) {
ret = sdio_writesb(func, addr, buf, len);
} else {
ret = sdio_writesb(func, addr, buf, 1000);
ret |= sdio_writesb(func, addr, &buf[1000], len-1000);
}
Based on the above, I am currently thinking there may be a bug in the
atmel-mci driver that causes this problem. Therefore, I will likely
contact that driver's maintainer next. I was just hoping to get your
insight in case there is something I am missing on the wl1271 side.
Thanks,
Logan
next reply other threads:[~2010-07-22 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 18:33 Logan Gunthorpe [this message]
2010-07-26 21:40 ` wl1271 with atmel-mci Logan Gunthorpe
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=4C488EEA.5020505@deltatee.com \
--to=logang@deltatee.com \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@nokia.com \
/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).