From: Stephen Boyd <swboyd@chromium.org> To: Mark Brown <broonie@kernel.org>, Oder Chiou <oder_chiou@realtek.com> Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>, Cheng-Yi Chiang <cychiang@chromium.org>, Shuming Fan <shumingf@realtek.com> Subject: [PATCH 1/3] ASoC: rt5682: Use dev_dbg() in rt5682_clk_check() Date: Mon, 3 Aug 2020 17:05:29 -0700 [thread overview] Message-ID: <20200804000531.920688-2-swboyd@chromium.org> (raw) In-Reply-To: <20200804000531.920688-1-swboyd@chromium.org> I see a spew of "sysclk/dai not set correctly" whenever I cat /sys/kernel/debug/clk/clk_summary on my device. This is because the master pointer isn't set yet in this driver. A user isn't going to be able to do much if this check is failing so this error message isn't really an error, it's more of a kernel debug message. Lower the priority to dev_dbg() so that it isn't so noisy. Cc: Cheng-Yi Chiang <cychiang@chromium.org> Cc: Shuming Fan <shumingf@realtek.com> Signed-off-by: Stephen Boyd <swboyd@chromium.org> --- sound/soc/codecs/rt5682.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/soc/codecs/rt5682.c b/sound/soc/codecs/rt5682.c index fab066a75ce0..ed9475f24aec 100644 --- a/sound/soc/codecs/rt5682.c +++ b/sound/soc/codecs/rt5682.c @@ -2482,7 +2482,7 @@ static int rt5682_set_bias_level(struct snd_soc_component *component, static bool rt5682_clk_check(struct rt5682_priv *rt5682) { if (!rt5682->master[RT5682_AIF1]) { - dev_err(rt5682->component->dev, "sysclk/dai not set correctly\n"); + dev_dbg(rt5682->component->dev, "sysclk/dai not set correctly\n"); return false; } return true; -- Sent by a computer, using git, on the internet
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <swboyd@chromium.org> To: Mark Brown <broonie@kernel.org>, Oder Chiou <oder_chiou@realtek.com> Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.com>, linux-kernel@vger.kernel.org, Shuming Fan <shumingf@realtek.com>, Cheng-Yi Chiang <cychiang@chromium.org> Subject: [PATCH 1/3] ASoC: rt5682: Use dev_dbg() in rt5682_clk_check() Date: Mon, 3 Aug 2020 17:05:29 -0700 [thread overview] Message-ID: <20200804000531.920688-2-swboyd@chromium.org> (raw) In-Reply-To: <20200804000531.920688-1-swboyd@chromium.org> I see a spew of "sysclk/dai not set correctly" whenever I cat /sys/kernel/debug/clk/clk_summary on my device. This is because the master pointer isn't set yet in this driver. A user isn't going to be able to do much if this check is failing so this error message isn't really an error, it's more of a kernel debug message. Lower the priority to dev_dbg() so that it isn't so noisy. Cc: Cheng-Yi Chiang <cychiang@chromium.org> Cc: Shuming Fan <shumingf@realtek.com> Signed-off-by: Stephen Boyd <swboyd@chromium.org> --- sound/soc/codecs/rt5682.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/soc/codecs/rt5682.c b/sound/soc/codecs/rt5682.c index fab066a75ce0..ed9475f24aec 100644 --- a/sound/soc/codecs/rt5682.c +++ b/sound/soc/codecs/rt5682.c @@ -2482,7 +2482,7 @@ static int rt5682_set_bias_level(struct snd_soc_component *component, static bool rt5682_clk_check(struct rt5682_priv *rt5682) { if (!rt5682->master[RT5682_AIF1]) { - dev_err(rt5682->component->dev, "sysclk/dai not set correctly\n"); + dev_dbg(rt5682->component->dev, "sysclk/dai not set correctly\n"); return false; } return true; -- Sent by a computer, using git, on the internet
next prev parent reply other threads:[~2020-08-04 0:05 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-04 0:05 [PATCH 0/3] ASoC: rt5682: Use clk APIs better Stephen Boyd 2020-08-04 0:05 ` Stephen Boyd 2020-08-04 0:05 ` Stephen Boyd [this message] 2020-08-04 0:05 ` [PATCH 1/3] ASoC: rt5682: Use dev_dbg() in rt5682_clk_check() Stephen Boyd 2020-08-04 0:05 ` [PATCH 2/3] ASoC: rt5682: Drop usage of __clk_get_name() Stephen Boyd 2020-08-04 0:05 ` Stephen Boyd 2020-08-04 0:05 ` [PATCH 3/3] ASoC: rt5682: Use clk_hw based APIs for registration Stephen Boyd 2020-08-04 0:05 ` Stephen Boyd 2020-08-18 16:56 ` [PATCH 0/3] ASoC: rt5682: Use clk APIs better Mark Brown 2020-08-18 16:56 ` Mark Brown
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=20200804000531.920688-2-swboyd@chromium.org \ --to=swboyd@chromium.org \ --cc=alsa-devel@alsa-project.org \ --cc=broonie@kernel.org \ --cc=cychiang@chromium.org \ --cc=linux-kernel@vger.kernel.org \ --cc=oder_chiou@realtek.com \ --cc=perex@perex.cz \ --cc=shumingf@realtek.com \ --cc=tiwai@suse.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: linkBe 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.