Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Ruslan Bilovol <ruslan.bilovol@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP2+: mux: correct wrong error messages
Date: Mon, 4 Mar 2013 09:35:30 -0800	[thread overview]
Message-ID: <20130304173530.GK11806@atomide.com> (raw)
In-Reply-To: <1359850510-32298-1-git-send-email-ruslan.bilovol@ti.com>

* Ruslan Bilovol <ruslan.bilovol@ti.com> [130202 16:18]:
> This is needed because the omap_mux_get_by_name()
> function calls the _omap_mux_get_by_name subfunction
> for each mux partition until needed mux is not found.
> As a result, we get messages like
> "Could not find signal XXX" for each partition
> where this mux name does not exist.
> 
> This patch fixes wrong error message in
> the _omap_mux_get_by_name() function moving it
> to the omap_mux_get_by_name() one and as result
> reduces noise in the kernel log.
> 
> My kernel log without this patch:
> [...]
> [    0.221801] omap_mux_init: Add partition: #2: wkup, flags: 3
> [    0.222045] _omap_mux_get_by_name: Could not find signal fref_clk0_out.sys_drm_msecure
> [    0.222137] _omap_mux_get_by_name: Could not find signal sys_nirq
> [    0.222167] _omap_mux_get_by_name: Could not find signal sys_nirq
> [    0.225006] _omap_mux_get_by_name: Could not find signal uart1_rx.uart1_rx
> [    0.225006] _omap_mux_get_by_name: Could not find signal uart1_rx.uart1_rx
> [    0.270111] _omap_mux_get_by_name: Could not find signal fref_clk4_out.fref_clk4_out
> [    0.273406] twl: not initialized
> 
> [...]
> 
> My kernel log with this patch:
> [...]
> [    0.221771] omap_mux_init: Add partition: #2: wkup, flags: 3
> [    0.222106] omap_mux_get_by_name: Could not find signal sys_nirq
> [    0.224945] omap_mux_get_by_name: Could not find signal uart1_rx.uart1_rx
> [    0.274536] twl: not initialized
> [...]
> 
> Signed-off-by: Ruslan Bilovol <ruslan.bilovol@ti.com>

Thanks applying into omap-for-v3.9-rc1/fixes.

Regards,

Tony


>  arch/arm/mach-omap2/mux.c |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm/mach-omap2/mux.c b/arch/arm/mach-omap2/mux.c
> index 6a217c9..9578ec0 100644
> --- a/arch/arm/mach-omap2/mux.c
> +++ b/arch/arm/mach-omap2/mux.c
> @@ -211,8 +211,6 @@ static int __init _omap_mux_get_by_name(struct omap_mux_partition *partition,
>  		return -EINVAL;
>  	}
>  
> -	pr_err("%s: Could not find signal %s\n", __func__, muxname);
> -
>  	return -ENODEV;
>  }
>  
> @@ -234,6 +232,8 @@ int __init omap_mux_get_by_name(const char *muxname,
>  		return mux_mode;
>  	}
>  
> +	pr_err("%s: Could not find signal %s\n", __func__, muxname);
> +
>  	return -ENODEV;
>  }
>  
> -- 
> 1.7.9.5
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2013-03-04 17:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-03  0:15 [PATCH] ARM: OMAP2+: mux: correct wrong error messages Ruslan Bilovol
2013-03-04 17:35 ` Tony Lindgren [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=20130304173530.GK11806@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=ruslan.bilovol@ti.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