From: Tony Lindgren <tony@atomide.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Ryan Grachek <ryan@edited.us>,
linux-wireless@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Wei Xu <xuwei5@hisilicon.com>,
Michal Simek <michal.simek@xilinx.com>,
"Reizer, Eyal" <eyalr@ti.com>,
John Stultz <john.stultz@linaro.org>,
Kalle Valo <kvalo@codeaurora.org>,
Valentin Schneider <valentin.schneider@arm.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] arm64: dts: zcu100-revC: Give wifi some time after power-on
Date: Thu, 24 Jan 2019 07:29:26 -0800 [thread overview]
Message-ID: <20190124152926.GM5720@atomide.com> (raw)
In-Reply-To: <efc793c8-da17-e267-851e-f08f097843ee@web.de>
* Jan Kiszka <jan.kiszka@web.de> [190124 08:29]:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Somewhere along recent changes to power control of the wl1831, power-on
> became very unreliable on the Ultra96, failing like this:
>
> wl1271_sdio: probe of mmc2:0001:1 failed with error -16
> wl1271_sdio: probe of mmc2:0001:2 failed with error -16
>
> After playing with some dt parameters and comparing to other users of
> this chip, it turned out we need some power-on delay to make things
> stable again. In contrast to those other users which define 200 ms,
> Ultra96 is already happy with 10 ms.
Good to hear this got sorted out, thanks everybody.
Acked-by: Tony Lindgren <tony@atomide.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-24 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 8:28 [PATCH v2] arm64: dts: zcu100-revC: Give wifi some time after power-on Jan Kiszka
2019-01-24 15:29 ` Tony Lindgren [this message]
2019-01-25 12:38 ` Michal Simek
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=20190124152926.GM5720@atomide.com \
--to=tony@atomide.com \
--cc=eyalr@ti.com \
--cc=jan.kiszka@web.de \
--cc=john.stultz@linaro.org \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=ryan@edited.us \
--cc=ulf.hansson@linaro.org \
--cc=valentin.schneider@arm.com \
--cc=xuwei5@hisilicon.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).