From: Ping-Ke Shih <pkshih@realtek.com>
To: Chukun Pan <amadeus@jmu.edu.cn>, "kvalo@kernel.org" <kvalo@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH 1/1] wifi: rtw88: 8822b: disable call trace when write RF mode table fail
Date: Mon, 23 Oct 2023 02:22:18 +0000 [thread overview]
Message-ID: <8dffe5f57c6948e1bca5f7cb3e40a781@realtek.com> (raw)
In-Reply-To: <20231022090901.430143-1-amadeus@jmu.edu.cn>
> -----Original Message-----
> From: Chukun Pan <amadeus@jmu.edu.cn>
> Sent: Sunday, October 22, 2023 5:09 PM
> To: kvalo@kernel.org
> Cc: Ping-Ke Shih <pkshih@realtek.com>; linux-kernel@vger.kernel.org; linux-wireless@vger.kernel.org;
> Chukun Pan <amadeus@jmu.edu.cn>
> Subject: RE: [PATCH 1/1] wifi: rtw88: 8822b: disable call trace when write RF mode table fail
>
> > _Why_ is that warning printed? Are your devices uncalibrated or are they
> > somehow else special?
>
> I don't know, but not only my rtl8822be wifi module will have this call trace
> every time when the driver probes. This can be considered a common problem.
> So I prefer to disable this call trace and use the driver warning instead.
>
Except to call trace, rtl8822be works well in your side? If so, you just
worry the verbose trace, right?
By the way, I tested two hardware version of rtl8822be, and they both are fine.
Ping-Ke
next prev parent reply other threads:[~2023-10-23 2:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 14:01 [PATCH 1/1] wifi: rtw88: 8822b: disable call trace when write RF mode table fail Chukun Pan
2023-10-13 1:11 ` Ping-Ke Shih
2023-10-13 2:38 ` Chukun Pan
2023-10-13 4:23 ` Kalle Valo
2023-10-22 9:09 ` Chukun Pan
2023-10-23 2:22 ` Ping-Ke Shih [this message]
2023-10-25 4:01 ` Chukun Pan
2023-10-23 8:21 ` Kalle Valo
2025-11-24 14:10 ` Bitterblue Smith
2025-11-25 0:30 ` Ping-Ke Shih
2025-11-27 14:39 ` Bitterblue Smith
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=8dffe5f57c6948e1bca5f7cb3e40a781@realtek.com \
--to=pkshih@realtek.com \
--cc=amadeus@jmu.edu.cn \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.