All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Varadarajan, Charulatha" <charu@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] OMAP: GPIO: Fix OMAP4 GPIO reg access issues
Date: Wed, 07 Apr 2010 08:09:30 -0700	[thread overview]
Message-ID: <87ljczguz9.fsf@deeprootsystems.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02C43ADE81@dbde02.ent.ti.com> (Charulatha Varadarajan's message of "Wed\, 7 Apr 2010 08\:02\:03 +0530")

"Varadarajan, Charulatha" <charu@ti.com> writes:

> ________________________________________
>> From: Kevin Hilman [khilman@deeprootsystems.com]
>> Sent: Wednesday, April 07, 2010 4:21 AM
>> To: Varadarajan, Charulatha
>> Cc: linux-omap@vger.kernel.org
>> Subject: Re: [PATCH] OMAP: GPIO: Fix OMAP4 GPIO reg access issues
>> 
>> Charulatha V <charu@ti.com> writes:
>> 
>> > Access to some of the OMAP4 GPIO registers are not properly handled.
>> > This patch fixes it.
>> >
>> 
>> Tested on... ?
>
> Tested on 3430SDP and 4430SDP.

Please update changelog accordingly.

>> > Signed-off-by: Charulatha V <charu@ti.com>
>> ---
>
> [...]
>
>> > @@ -1570,9 +1603,14 @@ static int gpio_is_input(struct gpio_bank *bank, int mask)
>> >               reg += OMAP7XX_GPIO_DIR_CONTROL;
>> >               break;
>> >       case METHOD_GPIO_24XX:
>> > -     case METHOD_GPIO_44XX:
>> >               reg += OMAP24XX_GPIO_OE;
>> >               break;
>> > +     case METHOD_GPIO_44XX:
>> > +             reg += OMAP4_GPIO_OE;
>> > +             break;
>> > +     default:
>> > +             WARN_ON(1);
>> > +             return -EINVAL;
>> 
>> If you add a WARN, please add a helpful string.
>
> Added this WARN in the same way as in other functions 
> of the same file.

That still doesn't make it helpful.

Repeating an error does not make it correct.

Kevin

      reply	other threads:[~2010-04-07 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22 14:38 [PATCH] OMAP: GPIO: Fix OMAP4 GPIO reg access issues Charulatha V
2010-04-06  8:21 ` Varadarajan, Charulatha
2010-04-06 22:51 ` Kevin Hilman
2010-04-07  2:32   ` Varadarajan, Charulatha
2010-04-07 15:09     ` 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=87ljczguz9.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=charu@ti.com \
    --cc=linux-omap@vger.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 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.