From: Nik Nyby <nikolas@gnu.org>
To: Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless@vger.kernel.org, pkshih@realtek.com
Subject: Re: rtl8821ae dbi read question
Date: Sun, 5 Nov 2017 23:09:15 -0500 [thread overview]
Message-ID: <ca520364-0d18-54c2-e6bc-b8245f8408ea@gnu.org> (raw)
In-Reply-To: <702e4270-dcf3-5916-daee-f2265e0da907@lwfinger.net>
On 11/05/2017 09:09 PM, Larry Finger wrote:
> Disabling all of _rtl8821ae_enable_aspm_back_door() may not be wise. We
> tried that patch as part of debugging.
>
> That routine consists of two mdio r/w sequences, and 3 dbi r/w
> sequences. The third one of the latter is only used for RTL8812AE, thus
> it can be ignored.
>
> What happens if you try disabling those r/w pairs one at a time? It is
> possible that one, or more of them, should be disabled when aspm is
> zero.
I first tried disabling only the mdio sequences, then the dbi sequences.
I was able to reproduce my problem in both cases. But I have found that
my problem is resolved by only removing the enable_aspm() call, and
leaving the call to _rtl8821ae_enable_aspm_back_door() intact.
If removing rtlpriv->intf_ops->enable_aspm(hw) is the same as setting
aspm=0, then it's possible I'm not setting the option correctly. But as
far as I can see right now, removing enable_aspm() is necessary for my
stable connection.
> It should not matter whether the driver is built in, or loaded as
> a module. Please note that I never build that code in as I always want
> the option of refreshing the driver without rebooting.
Thanks for the info - I'll do the same.
next prev parent reply other threads:[~2017-11-06 4:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 23:27 rtl8821ae dbi read question Nik Nyby
2017-11-05 16:50 ` Larry Finger
2017-11-05 20:53 ` Nik Nyby
2017-11-06 1:46 ` Larry Finger
2017-11-05 21:15 ` Nik Nyby
2017-11-05 21:29 ` James Cameron
2017-11-06 2:09 ` Larry Finger
2017-11-06 4:09 ` Nik Nyby [this message]
2017-11-06 13:52 ` Larry Finger
2017-11-19 0:39 ` Nik Nyby
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=ca520364-0d18-54c2-e6bc-b8245f8408ea@gnu.org \
--to=nikolas@gnu.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.