From: Tony Lindgren <tony@atomide.com>
To: Oskar Enoksson <enok@lysator.liu.se>
Cc: "H. Nikolaus Schaller" <hns@goldelico.com>, linux-omap@vger.kernel.org
Subject: Re: WL1271 on CM-T3730
Date: Mon, 22 Jun 2020 08:28:25 -0700 [thread overview]
Message-ID: <20200622152825.GK37466@atomide.com> (raw)
In-Reply-To: <5166bacd-428d-168c-edf4-a322274deac6@lysator.liu.se>
* Oskar Enoksson <enok@lysator.liu.se> [200621 22:01]:
> Correction: occasionally wl1271_sdio initialization still fails with error
> messages such as
>
> [ 46.961364] wl1271_sdio: probe of mmc1:0001:1 failed with error -16
> [ 46.967834] wl1271_sdio: probe of mmc1:0001:2 failed with error -16
>
> other times
>
> [ 27.302215][ T903] wl1271_sdio mmc1:0001:2: wl12xx_sdio_power_on: failed
> to get_sync(-22)
>
> or
> root@pte2000:~# ifup wlan0
> [ 53.799468][ T2420] wl1271_sdio mmc1:0001:2: wl12xx_sdio_power_on: failed
> to get_sync(-110)
> [ 53.840118][ T2420] wl1271_sdio mmc1:0001:2: wl12xx_sdio_power_on: failed
> to get_sync(-22)
> [ 53.879882][ T2420] wl1271_sdio mmc1:0001:2: wl12xx_sdio_power_on: failed
> to get_sync(-22)
> [ 53.888610][ T2420] wlcore: ERROR firmware boot failed despite 3 retries
> RTNETLINK answers: Invalid argument
> ifup: failed to bring up wlan0
Maybe try changing the wl12xx_vmmc2 startup-delay-us to something
higher like 70000 we usually have?
Regards,
Tony
next prev parent reply other threads:[~2020-06-22 15:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 21:04 WL1271 on CM-T3730 Oskar Enoksson
2020-06-16 15:39 ` Tony Lindgren
2020-06-17 10:44 ` Oskar Enoksson
2020-06-17 16:51 ` Tony Lindgren
2020-06-19 7:55 ` H. Nikolaus Schaller
2020-06-19 7:55 ` H. Nikolaus Schaller
2020-06-21 9:23 ` Oskar Enoksson
2020-06-21 22:00 ` Oskar Enoksson
2020-06-22 15:28 ` Tony Lindgren [this message]
2020-07-01 6:07 ` Oskar Enoksson
2020-07-02 16:40 ` Tony Lindgren
2020-06-22 15:24 ` Tony Lindgren
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=20200622152825.GK37466@atomide.com \
--to=tony@atomide.com \
--cc=enok@lysator.liu.se \
--cc=hns@goldelico.com \
--cc=linux-omap@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).