All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: Mark Jackson <mpfj-list@mimc.co.uk>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] ARM: OMAP: Clear GPMC bits when applying new setting
Date: Mon, 4 Mar 2013 09:37:06 -0800	[thread overview]
Message-ID: <20130304173706.GL11806@atomide.com> (raw)
In-Reply-To: <51126B2C.6080009@ti.com>

* Jon Hunter <jon-hunter@ti.com> [130206 06:43]:
> 
> On 02/06/2013 08:15 AM, Mark Jackson wrote:
> > When setting the GPMC device type, make sure any previous
> > bits are cleared down, before applying the new setting.
> > 
> > Signed-off-by: Mark Jackson <mpfj@newflow.co.uk>
> > ---
> >  arch/arm/mach-omap2/gpmc.c |    4 ++++
> >  1 file changed, 4 insertions(+)
> > 
> > diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
> > index 1adb2d4..026e786 100644
> > --- a/arch/arm/mach-omap2/gpmc.c
> > +++ b/arch/arm/mach-omap2/gpmc.c
> > @@ -613,6 +613,10 @@ int gpmc_cs_configure(int cs, int cmd, int wval)
> > 
> >  	case GPMC_CONFIG_DEV_TYPE:
> >  		regval  = gpmc_cs_read_reg(cs, GPMC_CS_CONFIG1);
> > +		/* clear 3 target bits */
> > +		regval &= ~(GPMC_CONFIG1_DEVICETYPE(3) |
> > +			    GPMC_CONFIG1_MUXADDDATA);
> 
> MUXADDDATA is actually a 2-bit field on current devices (OMAP4+ and
> AM335x). For OMAP2/3 devices it was only a one bit field. So it may be
> worth clearing both bits for all devices. For OMAP2 devices bit 8 is
> reserved but the TRM says to writes a 0, so clearing bit 8 on OMAP2/3
> devices should not be a problem. In fact bit 8 should read as 0 on OMAP2/3.
> 
> > +		/* set the proper value */
> >  		regval |= GPMC_CONFIG1_DEVICETYPE(wval);
> >  		if (wval == GPMC_DEVICETYPE_NOR)
> >  			regval |= GPMC_CONFIG1_MUXADDDATA;
> > 
> 
> Otherwise ...
> 
> Acked-by: Jon Hunter <jon-hunter@ti.com>

Mark, can you please repost this patch with Jon's comment addressed?

Thanks,

Tony

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 14:15 [PATCH] ARM: OMAP: Clear GPMC bits when applying new setting Mark Jackson
2013-02-06 14:32 ` Felipe Balbi
2013-02-06 14:39 ` Jon Hunter
2013-03-04 17:37   ` 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=20130304173706.GL11806@atomide.com \
    --to=tony@atomide.com \
    --cc=jon-hunter@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mpfj-list@mimc.co.uk \
    /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.