From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: yhchuang@realtek.com
Cc: kvalo@codeaurora.org, kernel@iuliancostan.com,
linux-wireless@vger.kernel.org, i@outv.im, trevor@shartrec.com
Subject: Re: [PATCH v1] rtw88: pci: disable aspm for platform inter-op with module parameter
Date: Wed, 10 Jun 2020 23:37:20 +0200 [thread overview]
Message-ID: <20200610213720.3sopcuimas375xl2@linutronix.de> (raw)
In-Reply-To: <20200605074703.32726-1-yhchuang@realtek.com>
On 2020-06-05 15:47:03 [+0800], yhchuang@realtek.com wrote:
> From: Yan-Hsuan Chuang <yhchuang@realtek.com>
>
> Some platforms cannot read the DBI register successfully for the
> ASPM settings. After the read failed, the bus could be unstable,
> and the device just became unavailable [1]. For those platforms,
> the ASPM should be disabled. But as the ASPM can help the driver
> to save the power consumption in power save mode, the ASPM is still
> needed. So, add a module parameter for them to disable it, then
> the device can still work, while others can benefit from the less
> power consumption that brings by ASPM enabled.
Can you set disable_aspm if rtw_dbi_read8() fails? Or make a test if it
is save to use?
If someone notices the warning they still have to search for the warning
in order to make the link towards loading the module with the
disable_aspm=1 paramter.
Is it known what causes the failure?
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=206411
> [2] Note that my lenovo T430 is the same.
Sebastian
next prev parent reply other threads:[~2020-06-10 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 7:47 [PATCH v1] rtw88: pci: disable aspm for platform inter-op with module parameter yhchuang
2020-06-10 21:37 ` Sebastian Andrzej Siewior [this message]
2020-06-16 11:06 ` Tony Chuang
2020-06-16 13:35 ` Sebastian Andrzej Siewior
2020-06-17 5:30 ` Tony Chuang
2020-06-17 7:29 ` Sebastian Andrzej Siewior
2020-07-15 9:00 ` Kalle Valo
2020-07-15 9:31 ` Tony Chuang
2020-06-20 19:53 ` Larry Finger
2020-07-15 9:10 ` Kalle Valo
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=20200610213720.3sopcuimas375xl2@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=i@outv.im \
--cc=kernel@iuliancostan.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=trevor@shartrec.com \
--cc=yhchuang@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.