From: Ping-Ke Shih <pkshih@realtek.com>
To: Sean Anderson <sean.anderson@linux.dev>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Bitterblue Smith" <rtl8821cerfe2@gmail.com>
Subject: RE: [PATCH v2] wifi: rtw89: Print just once for unknown C2H classes
Date: Fri, 1 Aug 2025 00:36:03 +0000 [thread overview]
Message-ID: <3de4e7b1ff574e90bef6d670d0e941a4@realtek.com> (raw)
In-Reply-To: <b4a69a44-bb9d-4c1d-b628-9204ed8c623e@linux.dev>
Sean Anderson <sean.anderson@linux.dev> wrote:
> On 7/29/25 23:42, Ping-Ke Shih wrote:
> > Ping-Ke Shih <pkshih@realtek.com> wrote:
> >> Sean Anderson <sean.anderson@linux.dev> wrote:
> >> > There are more unsupported functions than just LOWRT_RTY. Improve on
> >> > commit 3b66519b023b ("wifi: rtw89: phy: add dummy c2h handler to avoid
> >> > warning message") by printing a message just once when we first
> >> > encounter an unsupported class.
> >>
> >> Once I encounter an unsupported class/func, I'll check firmware team if the
> >> C2H events can be ignored. If so, I add a dummy function to avoid the message.
> >> If not, I should add code to handle the event.
> >>
> >> Do you want to see the message even though it only appears once?
> >>
> >> > Do the same for each unsupported func of
> >> > the supported classes. This prevents messages like
> >> >
> >> > rtw89_8922ae 0000:81:00.0: PHY c2h class 2 not support
> >
> > Is this a real example?
>
> This is a real example.
>
> > We have handled class 2 (RTW89_PHY_C2H_CLASS_DM), no?
>
> If func != RTW89_PHY_C2H_DM_FUNC_LOWRT_RTY then we fall through to the
> default case.
Oh. I see.
>
> > Please point out the class / func you encountered. Then I can look up vendor
> > driver or contact internal firmware team to know if we should implement or
> > just add a dummy function.
> >
> > If we defer it, I don't know when we can do it.
>
> rtw89_8922ae 0000:81:00.0: PHY c2h class 2 func 12 not supported
>
The C2H event handler has been added by [1].
[1] d31c42466b1a ("wifi: rtw89: phy: add C2H event handler for report of FW scan")
next prev parent reply other threads:[~2025-08-01 0:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 18:27 [PATCH] wifi: rtw89: Print only once for unsupported c2h classes Sean Anderson
2025-07-29 19:44 ` Bitterblue Smith
2025-07-29 20:44 ` [PATCH v2] wifi: rtw89: Print just once for unknown C2H classes Sean Anderson
2025-07-30 0:36 ` Ping-Ke Shih
2025-07-31 20:19 ` Sean Anderson
2025-08-01 0:30 ` Ping-Ke Shih
2025-08-01 14:39 ` Sean Anderson
2025-08-04 1:31 ` Ping-Ke Shih
2025-07-30 3:42 ` Ping-Ke Shih
2025-07-31 20:16 ` Sean Anderson
2025-08-01 0:36 ` Ping-Ke Shih [this message]
2025-08-01 14:39 ` Sean Anderson
2025-07-30 0:44 ` [PATCH] wifi: rtw89: Print only once for unsupported c2h classes Ping-Ke Shih
2025-08-04 1:33 ` 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=3de4e7b1ff574e90bef6d670d0e941a4@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@gmail.com \
--cc=sean.anderson@linux.dev \
/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.