From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Daniel Lenski <dlenski@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rtl8xxxu: increase polling timeout for firmware startup
Date: Fri, 20 May 2016 10:08:30 -0400 [thread overview]
Message-ID: <wrfj4m9svn35.fsf@redhat.com> (raw)
In-Reply-To: <CAOw_LSHnV+244fT7YvEoV+7VSH_+OoGFmZSdGK4a3NqB407VGQ@mail.gmail.com> (Daniel Lenski's message of "Thu, 19 May 2016 21:51:43 -0700")
Daniel Lenski <dlenski@gmail.com> writes:
> You're welcome, and thanks for writing this great driver. It really
> makes a huge difference for stability of the Yoga 13 wifi!
You're welcome! It made a big difference for my own Yoga 13 and it's
been an exciting project. I learned a lot in the process.
> Unfortunately, I ran into a case today where even 5000 loops was not
> enough after a cold boot. 5000 loops meant about 1.5 second delay
> between finishing the firmware checksum poll, while waiting for the
> firmware to start. It now appears to me that the number of required
> polling loops must be strongly bimodal.
>
> I added some logging, so that the driver reports to me the number of
> loops required for the firmware to start.
This is bizarre, I wonder if the hardware is having issues in your
laptop? Another thing to try would be to do an additional reset of the
chip and wait a bit before trying to load the firmware?
Cheers,
Jes
next prev parent reply other threads:[~2016-05-20 14:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 17:57 [PATCH] rtl8xxxu: increase polling timeout for firmware startup Dan Lenski
2016-05-18 17:57 ` [PATCH] rtl8xxxu: Increase default " Dan Lenski
2016-05-19 2:08 ` [PATCH] rtl8xxxu: increase " Jes Sorensen
2016-05-20 4:51 ` Daniel Lenski
2016-05-20 14:08 ` Jes Sorensen [this message]
2016-05-20 20:50 ` Daniel Lenski
2016-05-20 20:54 ` Daniel Lenski
2016-05-21 3:13 ` Jes Sorensen
2016-05-21 2:40 ` Daniel Lenski
2016-05-22 23:02 ` Dan Lenski
2016-05-23 19:24 ` Jes Sorensen
2016-05-23 21:47 ` Daniel Lenski
2016-05-31 15:04 ` Jes Sorensen
2016-05-31 17:59 ` Daniel Lenski
2016-05-31 18:24 ` Jes Sorensen
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=wrfj4m9svn35.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=dlenski@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).