From: Kevin Hilman <khilman@ti.com>
To: Ricardo Salveti de Araujo <ricardo.salveti@canonical.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP3630: PM: don't warn the user with a trace in case of PM34XX_ERRATUM
Date: Fri, 28 Jan 2011 14:10:40 -0800 [thread overview]
Message-ID: <871v3wbrxb.fsf@ti.com> (raw)
In-Reply-To: <1296187053-22186-1-git-send-email-ricardo.salveti@canonical.com> (Ricardo Salveti de Araujo's message of "Fri, 28 Jan 2011 01:57:33 -0200")
Ricardo Salveti de Araujo <ricardo.salveti@canonical.com> writes:
> In case in user has a OMAP3630 < ES1.2 the kernel should warn the user
> about the ERRATUM, but using printk instead of WARN_ON is already
> enough, as there is nothing else the user can do besides changing the
> board.
I agree, it doesn't need a full backtrace.
Minor comment below...
> Signed-off-by: Ricar
do Salveti de Araujo <ricardo.salveti@canonical.com>
> ---
> arch/arm/mach-omap2/cpuidle34xx.c | 2 +-
> arch/arm/mach-omap2/pm34xx.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/cpuidle34xx.c b/arch/arm/mach-omap2/cpuidle34xx.c
> index f7b22a1..abb9be0 100644
> --- a/arch/arm/mach-omap2/cpuidle34xx.c
> +++ b/arch/arm/mach-omap2/cpuidle34xx.c
> @@ -464,7 +464,7 @@ void omap_init_power_states(void)
> if (IS_PM34XX_ERRATUM(PM_SDRC_WAKEUP_ERRATUM_i583)) {
> omap3_power_states[OMAP3_STATE_C7].valid = 0;
> cpuidle_params_table[OMAP3_STATE_C7].valid = 0;
> - WARN_ONCE(1, "%s: core off state C7 disabled due to i583\n",
> + printk(KERN_WARNING "%s: core off state C7 disabled due to i583\n",
> __func__);
Please use pr_warn() instead.
> }
> }
> diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
> index a4aa192..983b543 100644
> --- a/arch/arm/mach-omap2/pm34xx.c
> +++ b/arch/arm/mach-omap2/pm34xx.c
> @@ -927,7 +927,7 @@ void omap3_pm_off_mode_enable(int enable)
> pwrst->pwrdm == core_pwrdm &&
> state == PWRDM_POWER_OFF) {
> pwrst->next_state = PWRDM_POWER_RET;
> - WARN_ONCE(1,
> + printk(KERN_WARNING
> "%s: Core OFF disabled due to errata i583\n",
> __func__);
ditto
> } else {
Thanks,
Kevin
prev parent reply other threads:[~2011-01-28 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 3:57 [PATCH] OMAP3630: PM: don't warn the user with a trace in case of PM34XX_ERRATUM Ricardo Salveti de Araujo
2011-01-28 22:10 ` Kevin Hilman [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=871v3wbrxb.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=ricardo.salveti@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox