All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 02/11] ARM: mach-shmobile: setup-r8a7740: add MERAM work-around
Date: Tue, 22 May 2012 10:17:17 +0000	[thread overview]
Message-ID: <20120522101717.GF22483@linux-sh.org> (raw)
In-Reply-To: <87fwatar29.wl%kuninori.morimoto.gx@renesas.com>

On Tue, May 22, 2012 at 12:07:57PM +0200, Laurent Pinchart wrote:
> On Tuesday 22 May 2012 13:41:54 Paul Mundt wrote:
> > As long as this exists outside of the MERAM register map and we don't have
> > to worry about the MERAM driver touching these values then having it as a
> > board-specific thing is probably fine. If it falls within the MERAM mapping
> > somewhere then the MERAM driver really should be dealing with it (or we can
> > set it as a board-specific thing when the MERAM driver isn't being used),
> > even if it is a magic value for the given CPU.
> 
> I agree. 0xFE950098 is outside of the MERAM registers address space (at least 
> in the SH7372 datasheet I have). I'm thus fine with setting the register in 
> board code.
> 
Ok, then we can just leave it in either the board or the CPU code.
Someone will want to verify that we do not have to do anything special
for this in the suspend/resume case, though. ie, losing the magic setting
after resume.

  parent reply	other threads:[~2012-05-22 10:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22  2:27 [PATCH 02/11] ARM: mach-shmobile: setup-r8a7740: add MERAM work-around Kuninori Morimoto
2012-05-22  2:56 ` Paul Mundt
2012-05-22  4:27 ` Kuninori Morimoto
2012-05-22  4:41 ` Paul Mundt
2012-05-22  8:04 ` kuninori.morimoto.gx
2012-05-22 10:07 ` Laurent Pinchart
2012-05-22 10:17 ` Paul Mundt [this message]
2012-05-23  0:23 ` Kuninori Morimoto

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=20120522101717.GF22483@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@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.