public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
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: Mon, 4 Aug 2025 01:31:31 +0000	[thread overview]
Message-ID: <639b56c577a0433cb49c85ce0abd5dca@realtek.com> (raw)
In-Reply-To: <198e2e23-5e75-4223-8d85-fba255bc7fd2@linux.dev>

Sean Anderson <sean.anderson@linux.dev> wrote:
> On 7/31/25 20:30, Ping-Ke Shih wrote:
> > Sean Anderson <sean.anderson@linux.dev> wrote:
> >> On 7/29/25 20:36, Ping-Ke Shih 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?
> >>
> >> I mean, maybe it should just be a debug? Are these messages useful for anyone
> >> other than the developers?
> >
> > Yes, this could just be a debug. However, developers normally don't turn on
> > debug mask, so using rtw89_info is to clearly remind developers to pay
> > attention on this lack of C2H handler. And, I suppose developers must handle
> > this when they see flooding messages.
> 
> Well, regular users get this too. It is really unnecessary to print
> thousands of messages when they are completely benign.
> 
> >>
> >> Maybe we should just print only the very first unsupported message at info level
> >> and print the rest at debug.
> >
> > I'm afraid developers will ignore or miss the messages. To reduce messages
> > is fine to me , but more important is to look up vendor driver to see if
> > the C2H handler is necessary.
> 
> OK, so we should print exactly once for each class/func.
> 

I sent a patchset [1] to print exactly once, but I don't add bitmap for every
printed class/func, because it seems to be unnecessary to add much code to 
handle the case which should be handled during development. 

Please help to try if this patchset can resolve thousands of message in your
side. 

[1] https://lore.kernel.org/linux-wireless/20250804012234.8913-1-pkshih@realtek.com/T/#t


  reply	other threads:[~2025-08-04  1:31 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 [this message]
2025-07-30  3:42     ` Ping-Ke Shih
2025-07-31 20:16       ` Sean Anderson
2025-08-01  0:36         ` Ping-Ke Shih
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=639b56c577a0433cb49c85ce0abd5dca@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox