All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pkshih <pkshih@realtek.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: "Larry.Finger@lwfinger.net" <Larry.Finger@lwfinger.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: Funny log entries for rtw88_8821ce
Date: Fri, 11 Feb 2022 00:25:27 +0000	[thread overview]
Message-ID: <ef1b6cf1c82c49faab84610ad960f72a@realtek.com> (raw)
In-Reply-To: <87mtiy3iha.fsf@kernel.org>


> -----Original Message-----
> From: Kalle Valo <kvalo@kernel.org>
> Sent: Thursday, February 10, 2022 10:27 PM
> To: Pkshih <pkshih@realtek.com>
> Cc: Larry.Finger@lwfinger.net; linux-wireless@vger.kernel.org
> Subject: Re: Funny log entries for rtw88_8821ce
> 
> Pkshih <pkshih@realtek.com> writes:
> 
> > Then, I have a question about the message of setting SAR:
> > 	rtw_info(rtwdev, "On freq %u to %u, set SAR %d in 1/%lu dBm\n"
> >
> > When a user sets SAR via iw, this message can reflect the action performed
> > by driver. Is this rtw_info acceptable?
> 
> In general the preference for user space commands is not to print
> anything to the log when debug messages are disabled, but of course
> there can be exceptions if the reasons are good. Why do you want to
> print this always? What benefit does it bring for the user?
> 

Understand. My original thinking still focus on debug purpose.

Because the SAR doesn't have a 'get' method to check status, and it affects
TX power but a user can't be aware that clearly. If someone told me his
laptop has low wifi performance, this message can be a good clue to address
the problem.

Fortunately, I still can use debugfs to debug this case, so I will change
this message to debug level.

--
Ping-Ke


      reply	other threads:[~2022-02-11  0:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 22:53 Funny log entries for rtw88_8821ce Larry Finger
2022-02-01  6:26 ` Pkshih
2022-02-03 20:06   ` Larry Finger
2022-02-08  9:01     ` Kalle Valo
2022-02-08 12:02       ` Pkshih
2022-02-10 14:26         ` Kalle Valo
2022-02-11  0:25           ` Pkshih [this message]

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=ef1b6cf1c82c49faab84610ad960f72a@realtek.com \
    --to=pkshih@realtek.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=kvalo@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.