linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Ali Ghandour <gandour.ali@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: Lenovo LOQ rtw_8852be
Date: Tue, 12 Dec 2023 06:01:40 +0000	[thread overview]
Message-ID: <d1675f8f84de45a5a44bc36041816762@realtek.com> (raw)
In-Reply-To: <CAOE0c94tf8y2hv0QHKEiuo5a7Ly=oJAw+g4Uh6BktHOMdbWY1Q@mail.gmail.com>



> -----Original Message-----
> From: Ali Ghandour <gandour.ali@gmail.com>
> Sent: Tuesday, December 12, 2023 1:36 PM
> To: Ping-Ke Shih <pkshih@realtek.com>
> Cc: linux-wireless@vger.kernel.org
> Subject: Re: Lenovo LOQ rtw_8852be
> 
> > Please try below workaround patch to ignore the setting. I have tried that, and
> > in my side it still works without obvious problem. I will check internally to
> > check how much this can affect. If not, I would ignore this if certain platform
> > like yours can't access PCI space over 0x100.
> 
> I was able to connect. Thanks a lot Ping-Ke!
> 

Good. Please use it as usual and monitor if it works stable. I would like
take your results as reference to decide how I can modify the driver. 

> [  609.796171] rtw89_8852be 0000:09:00.0: failed to set CLKREQ Delay
> [  609.796175] rtw89_8852be 0000:09:00.0: failed to set CLKREQ_L1, ret=-22
> [  609.796177] rtw89_8852be 0000:09:00.0: failed to read ASPM Delay
> [  609.796177] rtw89_8852be 0000:09:00.0: failed to read ASPM Delay
> [  609.796178] rtw89_8852be 0000:09:00.0: failed to set ASPM L1, ret=-22

These mean we fail to access more PCI config space over 0x100. I will
consider these cases as well.

Ping-Ke



  reply	other threads:[~2023-12-12  6:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1700948088-16140-mlmmj-666d2532@vger.kernel.org>
2023-11-25 21:35 ` Lenovo LOQ rtw_8852be Ali Ghandour
2023-11-27  1:42   ` Ping-Ke Shih
2023-11-27  6:01     ` Ali Ghandour
2023-11-27  6:19       ` Ali Ghandour
2023-11-28  1:21         ` Ping-Ke Shih
2023-12-02  9:23           ` Ali Ghandour
2023-12-05  0:39             ` Ping-Ke Shih
2023-12-05  6:12               ` Ali Ghandour
2023-12-06  2:41                 ` Ping-Ke Shih
2023-12-10  6:24                   ` Ali Ghandour
2023-12-11  1:53                     ` Ping-Ke Shih
2023-12-12  5:36                       ` Ali Ghandour
2023-12-12  6:01                         ` Ping-Ke Shih [this message]
2023-12-26  3:42                         ` Ping-Ke Shih
     [not found]                           ` <CAOE0c95hkCdoKksAO5KhfVPuH1r8bpWXyM4Q_B+R2N-mJFz4yA@mail.gmail.com>
2024-01-03  0:13                             ` Ping-Ke Shih

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=d1675f8f84de45a5a44bc36041816762@realtek.com \
    --to=pkshih@realtek.com \
    --cc=gandour.ali@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).