From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Kyle Evans <kvans32@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: sdio failure to initialize on warm boot.
Date: Fri, 19 Jan 2018 09:21:50 +0100 [thread overview]
Message-ID: <5A61AA9E.6000505@broadcom.com> (raw)
In-Reply-To: <20180118172804.GA1170@localhost.localdomain>
On 1/18/2018 6:50 PM, Kyle Evans wrote:
> * Arend van Spriel <arend.vanspriel@broadcom.com>:
>> On 1/12/2018 9:18 PM, Kyle Evans wrote:
>>> 2) After reboot I get this nasty error...
>>> [ 0.000000] Kernel command line: console=tty0 selinux=0
>>> video=1280x800 root=/dev/mmcblk1p1 brcmfmac.bebug=0x20000
>>> [ 2.269750] mmc0: Invalid maximum block size, assuming 512 bytes
>>> [ 2.330010] mmc0: SDHCI controller on c8000000.sdhci [c8000000.sdhci]
>>> using ADMA
>>> [ 2.645242] mmc0: error -110 whilst initialising SDIO card
>>
>> Ok. I suppose you mean a warm reboot. So I suppose the card is not
>> properly power cycled. If your SDHCI controller driver (is it
>> sdhci-acpi?) is loaded as a module, you could try to unload it and load
>> it again. Let me know if that works for you to confirm my guess.
>
> Your guess is correct. The following brings up wifi after failure to do
> so during warm boot.
>
> modprobe -r sdhci-tegra; modprobe sdhci-tegra;
Do you know if your uses a device tree and where I can find it?
Typically, there is a GPIO to the wifi device that needs to be toggled
using mmc powerseq.
Regards,
Arend
next prev parent reply other threads:[~2018-01-19 8:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 12:51 brcmfmac4329-sdio firmware load failed Kyle Evans
2018-01-10 8:47 ` Arend van Spriel
2018-01-12 20:18 ` Kyle Evans
2018-01-13 9:19 ` Arend van Spriel
2018-01-16 1:20 ` Kyle Evans
2018-01-16 20:18 ` Arend van Spriel
2018-01-18 17:50 ` sdio failure to initialize on warm boot Kyle Evans
2018-01-19 8:21 ` Arend van Spriel [this message]
2018-01-19 16:05 ` Kyle Evans
2018-01-22 9:22 ` Arend van Spriel
2018-01-26 10:45 ` Kyle Evans
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=5A61AA9E.6000505@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=kvans32@gmail.com \
--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).