public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Ranjith Lohithakshan <ranjithl@ti.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"tony@atomide.com" <tony@atomide.com>
Subject: Re: [PATCH] omap: Remove DEBUGFS dependency for mux name checking
Date: Wed, 17 Feb 2010 22:11:50 +0530	[thread overview]
Message-ID: <4B7C1C4E.2090709@ti.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59301E5774A31@dbde02.ent.ti.com>

Sanjeev,

On Wed, 17-Feb-10 3:46 PM +0530, Premi, Sanjeev wrote:
>> -----Original Message-----
>> From: linux-omap-owner@vger.kernel.org 
>> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of 
>> Lohithakshan, Ranjith
>> Sent: Wednesday, February 17, 2010 11:48 AM
>> To: linux-omap@vger.kernel.org
>> Cc: tony@atomide.com; Lohithakshan, Ranjith
>> Subject: [PATCH] omap: Remove DEBUGFS dependency for mux name checking
>>
>> The check for a valid mux name should be performed regardless 
>> of whether
>> DEBUGFS is enabled or not.
>>
>> This fixes the issue currently seen with boards not booting up
>> if DEBUGFS is not enabled in defconfig.
>>
>> Signed-off-by: Ranjith Lohithakshan <ranjithl@ti.com>
>> ---
>>  arch/arm/mach-omap2/mux.c |    2 +-
>>  1 files changed, 1 insertions(+), 1 deletions(-)
>>
> 
> Ranjith,
> 
> For better readability, I suggest the following:
> 
> diff --git a/arch/arm/mach-omap2/mux.c b/arch/arm/mach-omap2/mux.c
> index 19001dd..7c0c4ad 100644
> --- a/arch/arm/mach-omap2/mux.c
> +++ b/arch/arm/mach-omap2/mux.c
> @@ -960,16 +960,14 @@ static void __init omap_mux_init_list(struct omap_mux *sup
>         while (superset->reg_offset !=  OMAP_MUX_TERMINATOR) {
>                 struct omap_mux *entry;
> 
> -#ifndef CONFIG_OMAP_MUX
> -               /* Skip pins that are not muxed as GPIO by bootloader */
> -               if (!OMAP_MODE_GPIO(omap_mux_read(superset->reg_offset))) {
> +#ifdef CONFIG_OMAP_MUX
> +               if (!superset->muxnames || !superset->muxnames[0]) {
>                         superset++;
>                         continue;
>                 }
> -#endif
> -
> -#if defined(CONFIG_OMAP_MUX) && defined(CONFIG_DEBUG_FS)
> -               if (!superset->muxnames || !superset->muxnames[0]) {
> +#else
> +               /* Skip pins that are not muxed as GPIO by bootloader */
> +               if (!OMAP_MODE_GPIO(omap_mux_read(superset->reg_offset))) {
>                         superset++;
>                         continue;

Sounds good. I will issue an updated patch shortly.

 - Ranjith

> Best regards,
> Sanjeev
> 
> 
>> diff --git a/arch/arm/mach-omap2/mux.c b/arch/arm/mach-omap2/mux.c
>> index 986077f..1a6ff8f 100644
>> --- a/arch/arm/mach-omap2/mux.c
>> +++ b/arch/arm/mach-omap2/mux.c
>> @@ -969,7 +969,7 @@ static void __init 
>> omap_mux_init_list(struct omap_mux *superset)
>>  		}
>>  #endif
>>  
>> -#if defined(CONFIG_OMAP_MUX) && defined(CONFIG_DEBUG_FS)
>> +#ifdef CONFIG_OMAP_MUX
>>  		if (!superset->muxnames || !superset->muxnames[0]) {
>>  			superset++;
>>  			continue;
>> -- 
>> 1.6.2.4
>>
>> --
>> 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:[~2010-02-17 16:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17  6:18 [PATCH] omap: Remove DEBUGFS dependency for mux name checking Ranjith Lohithakshan
2010-02-17 10:16 ` Premi, Sanjeev
2010-02-17 16:41   ` Ranjith Lohithakshan [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=4B7C1C4E.2090709@ti.com \
    --to=ranjithl@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=premi@ti.com \
    --cc=tony@atomide.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