All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Kim Kyuwon <chammoru@gmail.com>
Cc: David Brownell <david-b@pacbell.net>,
	OMAP <linux-omap@vger.kernel.org>,
	Manikandan Pillai <mani.pillai@ti.com>
Subject: Re: [patch 2.6.29-rc3-omap-git] omap3: gpio pin config bugfixes
Date: Wed, 11 Feb 2009 16:45:05 -0800	[thread overview]
Message-ID: <20090212004500.GG13748@atomide.com> (raw)
In-Reply-To: <4d34a0a70902090424n5e64a4fjeae8ce20bd4fafd0@mail.gmail.com>

* Kim Kyuwon <chammoru@gmail.com> [090209 04:25]:
> Hi,
> 
> On Mon, Feb 9, 2009 at 1:55 PM, David Brownell <david-b@pacbell.net> wrote:
> > From: David Brownell <dbrownell@users.sourceforge.net>
> >
> > Bugfix several GPIO mux configurations which didn't enable the
> > input drivers, but weren't named as e.g. ..._GPIO141_OUT.
> > These bugs were added quite recently, for OMAP3 EVM support.
> >
> > To help avoid such bugs in the future, update the comment to
> > clarify the rule:  always use PIN_INPUT, unless the name uses
> > that name suffix, to be crystal-clear on the signal's use as
> > output-only.
> >
> > (Also adds GPIO-63, for the EVM's MMC-1 writeprotect switch.
> > Presumably that works right...)
> >
> > Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
> > ---
> >
> >  arch/arm/mach-omap2/mux.c             |   13 ++++++++-----
> >  arch/arm/plat-omap/include/mach/mux.h |    1 +
> >  2 files changed, 9 insertions(+), 5 deletions(-)
> >
> > --- a/arch/arm/mach-omap2/mux.c
> > +++ b/arch/arm/mach-omap2/mux.c
> > @@ -453,6 +453,7 @@ MUX_CFG_34XX("AC1_3430_USB3FS_PHY_MM3_TX
> >
> >
> >  /* 34XX GPIO - bidirectional, unless the name has an "_OUT" suffix.
> > + * (Always specify PIN_INPUT, except for names suffixed by "_OUT".)
> >  * No internal pullup/pulldown without "_UP" or "_DOWN" suffix.
> >  */
> >  MUX_CFG_34XX("AH8_34XX_GPIO29", 0x5fa,
> > @@ -460,17 +461,19 @@ MUX_CFG_34XX("AH8_34XX_GPIO29", 0x5fa,
> >  MUX_CFG_34XX("J25_34XX_GPIO170", 0x1c6,
> >                OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_INPUT)
> >  MUX_CFG_34XX("AF26_34XX_GPIO0", 0x1e0,
> > -               OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_OUTPUT)
> > +               OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_INPUT)
> >  MUX_CFG_34XX("AF22_34XX_GPIO9", 0xa18,
> > -               OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_OUTPUT)
> > +               OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_INPUT)
> > +MUX_CFG_34XX("L8_34XX_GPIO63", 0x0ce,
> > +               OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_INPUT)
> >  MUX_CFG_34XX("AF6_34XX_GPIO140_UP", 0x16c,
> >                OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_INPUT_PULLUP)
> >  MUX_CFG_34XX("AE6_34XX_GPIO141", 0x16e,
> > -               OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_OUTPUT)
> > +               OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_INPUT)
> >  MUX_CFG_34XX("AF5_34XX_GPIO142", 0x170,
> > -               OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_OUTPUT)
> > +               OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_INPUT)
> >  MUX_CFG_34XX("AE5_34XX_GPIO143", 0x172,
> > -               OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_OUTPUT)
> > +               OMAP34XX_MUX_MODE4 | OMAP34XX_PIN_INPUT)
> >
> >  };
> >
> 
> So the thing is, OMAP34XX_PIN_INPUT doens't mean input-only, but
> input-and-output. And OMAP34XX_PIN_OUTPUT doen't mean output, but output-only.
> Names of macros are really confusing me. Shouldn't we change names of these
> macros first? For example,
> OMAP34XX_PIN_INPUT -> OMAP34XX_PIN_INPUT_EN
> OMAP34XX_PIN_OUTPUT -> OMAP34XX_PIN_OUTPUT_ONLY

I like this idea to cut down on confusion.

Tony


> > --- a/arch/arm/plat-omap/include/mach/mux.h
> > +++ b/arch/arm/plat-omap/include/mach/mux.h
> > @@ -792,6 +792,7 @@ enum omap34xx_index {
> >        J25_34XX_GPIO170,
> >        AF26_34XX_GPIO0,
> >        AF22_34XX_GPIO9,
> > +       L8_34XX_GPIO63,
> >        AF6_34XX_GPIO140_UP,
> >        AE6_34XX_GPIO141,
> >        AF5_34XX_GPIO142,
> > --
> > 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
> >
> 
> 
> 
> -- 
> Kim Kyuwon
> --
> 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:[~2009-02-12  0:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09  4:55 [patch 2.6.29-rc3-omap-git] omap3: gpio pin config bugfixes David Brownell
2009-02-09 12:24 ` Kim Kyuwon
2009-02-12  0:45   ` Tony Lindgren [this message]
2009-02-12  1:51     ` David Brownell
2009-02-27 22:46 ` Tony Lindgren
2009-02-27 22:48   ` [APPLIED] " Tony Lindgren

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=20090212004500.GG13748@atomide.com \
    --to=tony@atomide.com \
    --cc=chammoru@gmail.com \
    --cc=david-b@pacbell.net \
    --cc=linux-omap@vger.kernel.org \
    --cc=mani.pillai@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 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.