From: Hans de Goede <hdegoede@redhat.com>
To: linux-mmc <linux-mmc@vger.kernel.org>,
Arend van Spriel <arend@broadcom.com>
Subject: Avoiding / recovering from end bit errors with sdio device (bcm43362)
Date: Mon, 26 May 2014 11:13:10 +0200 [thread overview]
Message-ID: <538305A6.5000105@redhat.com> (raw)
Hi All,
Every few hours (on average) the bcm43362 sdio wifi on 2 different
model allwinner boards I've throws an EBE error. The error handling
code successfully send a stop command after this, but still any
other command after that ends with a data time out error (which again
gets followed by a successful stop command).
Does this indicate a problem with the sdio device (driver), or could
this also be triggered by a bug in the mmc host driver?
One thing worth noticing hereby is that the brcmfmac drivers sdio
drivestrength table mentions that it is for 1.8v signalling, where
as the SoC side of things is using 3.3v signalling (this cannot
be changed).
Any help to further debug this would be greatly appreciated.
Thanks & Regards,
Hans
reply other threads:[~2014-05-26 9:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=538305A6.5000105@redhat.com \
--to=hdegoede@redhat.com \
--cc=arend@broadcom.com \
--cc=linux-mmc@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).