From: Viresh Kumar <viresh.kumar@linaro.org>
To: Frank Wunderlich <linux@fw-web.de>
Cc: linux-pm@vger.kernel.org,
Frank Wunderlich <frank-w@public-files.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC v1] opp: add config option for debug
Date: Thu, 5 May 2022 11:28:57 +0530 [thread overview]
Message-ID: <20220505055857.bqjm72qkzwcbuvuh@vireshk-i7> (raw)
In-Reply-To: <20220504174823.156709-1-linux@fw-web.de>
On 04-05-22, 19:48, Frank Wunderlich wrote:
> From: Frank Wunderlich <frank-w@public-files.de>
>
> Currently OPP debug is enabled by DEBUG_DRIVER option. This is generic
> driver debug and opp floods serial console. This is annoying if opp is
> not needed so give it an additional config-key.
>
> Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
> ---
> drivers/base/Kconfig | 1 +
> drivers/opp/Kconfig | 7 +++++++
> drivers/opp/Makefile | 2 +-
> 3 files changed, 9 insertions(+), 1 deletion(-)
Isn't something like Dynamic Debug helpful here ?
--
viresh
next prev parent reply other threads:[~2022-05-05 5:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 17:48 [RFC v1] opp: add config option for debug Frank Wunderlich
2022-05-04 18:24 ` Greg Kroah-Hartman
2022-05-05 17:50 ` Frank Wunderlich
2022-05-05 17:57 ` Greg Kroah-Hartman
2022-05-05 5:58 ` Viresh Kumar [this message]
2022-05-05 15:54 ` Aw: " Frank Wunderlich
2022-05-05 17:38 ` Greg Kroah-Hartman
2022-05-06 4:06 ` Viresh Kumar
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=20220505055857.bqjm72qkzwcbuvuh@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=frank-w@public-files.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@fw-web.de \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--cc=vireshk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).