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: Mon, 11 Dec 2023 01:53:24 +0000 [thread overview]
Message-ID: <973fe7f5ec2c474c8a88f8933c7dde83@realtek.com> (raw)
In-Reply-To: <CAOE0c94UMKymy8mV2unbNo9CRe9n0pUmg6dGQ-xnRRKZvMxNJA@mail.gmail.com>
> -----Original Message-----
> From: Ali Ghandour <gandour.ali@gmail.com>
> Sent: Sunday, December 10, 2023 2:24 PM
> To: Ping-Ke Shih <pkshih@realtek.com>
> Cc: linux-wireless@vger.kernel.org
> Subject: Re: Lenovo LOQ rtw_8852be
>
> It ended up showing 4096.
But still not work. PCI code is hard to me.
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.
@@ -2061,6 +2061,9 @@ static int rtw89_pci_auto_refclk_cal(struct rtw89_dev *rtwdev, bool autook_en)
if (chip_id != RTL8852B && chip_id != RTL8851B)
return 0;
+ printk("no auto_refclk_cal\n");
+ return 0;
+
ret = rtw89_pci_read_config_byte(rtwdev, RTW89_PCIE_PHY_RATE, &val8);
if (ret) {
rtw89_err(rtwdev, "[ERR]pci config read %X\n",
Ping-Ke
next prev parent reply other threads:[~2023-12-11 1:53 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 [this message]
2023-12-12 5:36 ` Ali Ghandour
2023-12-12 6:01 ` Ping-Ke Shih
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=973fe7f5ec2c474c8a88f8933c7dde83@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 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.