From: Kalle Valo <kvalo@codeaurora.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Brian Norris <briannorris@chromium.org>,
Ping-Ke Shih <pkshih@realtek.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
netdev@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH 04/24] rtw89: add debug files
Date: Mon, 05 Jul 2021 11:08:07 +0300 [thread overview]
Message-ID: <87k0m5i3o8.fsf@codeaurora.org> (raw)
In-Reply-To: <20210702175740.5cdhmfp4ldiv6tn7@pengutronix.de> (Oleksij Rempel's message of "Fri, 2 Jul 2021 19:57:40 +0200")
Oleksij Rempel <o.rempel@pengutronix.de> writes:
> On Fri, Jul 02, 2021 at 10:08:53AM -0700, Brian Norris wrote:
>> On Fri, Jul 2, 2021 at 12:23 AM Oleksij Rempel <o.rempel@pengutronix.de> wrote:
>> > On Fri, Jun 18, 2021 at 02:46:05PM +0800, Ping-Ke Shih wrote:
>> > > +#ifdef CONFIG_RTW89_DEBUGMSG
>> > > +unsigned int rtw89_debug_mask;
>> > > +EXPORT_SYMBOL(rtw89_debug_mask);
>> > > +module_param_named(debug_mask, rtw89_debug_mask, uint, 0644);
>> > > +MODULE_PARM_DESC(debug_mask, "Debugging mask");
>> > > +#endif
>> >
>> >
>> > For dynamic debugging we usually use ethtool msglvl.
>> > Please, convert all dev_err/warn/inf.... to netif_ counterparts
>>
>> Have you ever looked at a WiFi driver?
>
> Yes. You can parse the kernel log for my commits.
>
>> I haven't seen a single one that uses netif_*() for logging.
>> On the other hand, almost every
>> single one has a similar module parameter or debugfs knob for enabling
>> different types of debug messages.
>>
>> As it stands, the NETIF_* categories don't really align at all with
>> the kinds of message categories most WiFi drivers support. Do you
>> propose adding a bunch of new options to the netif debug feature?
>
> Why not? It make no sense or it is just "it is tradition, we never do
> it!" ?
>
> Even dynamic printk provide even more granularity. So module parameter looks
> like stone age against all existing possibilities.
I'm all for improving wireless driver debugging features, but let's
please keep that as a separate thread from reviewing new drivers. I
think there are 4-5 new drivers in the queue at the moment so to keep
all this manageable let's have the review process as simple as possible,
please.
Using a module parameter for setting the debug mask is a standard
feature in wireless drivers so it shouldn't block rtw89. If we want a
generic debug framework for wireless drivers, an rfc patch for an
existing upstream wireless driver is a good way to get that discussion
forward.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-07-05 8:08 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 6:46 [PATCH 00/24] rtw89: add Realtek 802.11ax driver Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 01/24] rtw89: add CAM files Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 02/24] rtw89: add BT coexistence files Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 03/24] rtw89: add core and trx files Ping-Ke Shih
2021-07-09 17:32 ` Oleksij Rempel
2021-07-12 6:23 ` Pkshih
2021-07-15 18:57 ` Brian Norris
2021-07-16 2:00 ` Pkshih
2021-06-18 6:46 ` [PATCH 04/24] rtw89: add debug files Ping-Ke Shih
2021-07-02 7:23 ` Oleksij Rempel
2021-07-02 17:08 ` Brian Norris
2021-07-02 17:57 ` Oleksij Rempel
2021-07-02 18:38 ` Brian Norris
2021-07-02 19:32 ` Oleksij Rempel
2021-07-02 20:00 ` Brian Norris
2021-07-03 4:15 ` Oleksij Rempel
2021-07-13 1:40 ` Brian Norris
2021-07-05 8:58 ` Pkshih
2021-07-05 9:09 ` Oleksij Rempel
2021-07-05 8:08 ` Kalle Valo [this message]
2021-07-05 9:23 ` Oleksij Rempel
2021-07-05 8:58 ` Pkshih
2021-07-13 1:57 ` Brian Norris
2021-07-13 4:50 ` Oleksij Rempel
2021-07-13 11:26 ` Pkshih
2021-06-18 6:46 ` [PATCH 05/24] rtw89: add efuse files Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 06/24] rtw89: add files to download and communicate with firmware Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 07/24] rtw89: add MAC files Ping-Ke Shih
2021-07-09 17:38 ` Oleksij Rempel
2021-07-09 18:16 ` Johannes Berg
2021-07-10 4:58 ` Oleksij Rempel
2021-07-12 1:51 ` Pkshih
2021-07-12 6:23 ` Pkshih
2021-06-18 6:46 ` [PATCH 08/24] rtw89: implement mac80211 ops Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 09/24] rtw89: add pci files Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 10/24] rtw89: add phy files Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 11/24] rtw89: define register names Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 12/24] rtw89: add regulatory support Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 13/24] rtw89: 8852a: add 8852a specific files Ping-Ke Shih
2021-07-10 5:27 ` Oleksij Rempel
2021-07-12 6:24 ` Pkshih
2021-06-18 6:46 ` [PATCH 14/24] rtw89: 8852a: add 8852a RFK files Ping-Ke Shih
2021-07-09 17:41 ` Oleksij Rempel
2021-07-12 6:23 ` Pkshih
2021-07-15 3:33 ` Pkshih
2021-07-15 3:59 ` Oleksij Rempel
2021-06-18 6:46 ` [PATCH 15/24] rtw89: 8852a: add 8852a RFK tables Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 16/24] rtw89: 8852a: add 8852a tables (1 of 5) Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 17/24] rtw89: 8852a: add 8852a tables (2 " Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 18/24] rtw89: 8852a: add 8852a tables (3 " Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 19/24] rtw89: 8852a: add 8852a tables (4 " Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 20/24] rtw89: 8852a: add 8852a tables (5 " Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 21/24] rtw89: add ser to recover error reported by firmware Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 22/24] rtw89: add PS files Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 23/24] rtw89: add SAR files Ping-Ke Shih
2021-06-18 6:46 ` [PATCH 24/24] rtw89: add Kconfig and Makefile Ping-Ke Shih
2021-06-19 3:18 ` kernel test robot
2021-06-19 3:18 ` kernel test robot
2021-06-19 3:18 ` kernel test robot
2021-06-19 3:18 ` kernel test robot
2021-06-25 8:54 ` Pkshih
2021-06-25 8:54 ` Pkshih
2021-06-18 7:11 ` [PATCH 00/24] rtw89: add Realtek 802.11ax driver Pkshih
2021-06-23 6:29 ` Aaron Ma
2021-06-30 4:52 ` Aaron Ma
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=87k0m5i3o8.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=briannorris@chromium.org \
--cc=kernel@pengutronix.de \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pkshih@realtek.com \
/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.