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 02:56:36 +0000	[thread overview]
Message-ID: <20120522025635.GA22483@linux-sh.org> (raw)
In-Reply-To: <87fwatar29.wl%kuninori.morimoto.gx@renesas.com>

On Mon, May 21, 2012 at 07:27:13PM -0700, kuninori.morimoto.gx@renesas.com wrote:
> --- a/arch/arm/mach-shmobile/setup-r8a7740.c
> +++ b/arch/arm/mach-shmobile/setup-r8a7740.c
> @@ -324,6 +324,24 @@ static struct platform_device *r8a7740_late_devices[] __initdata = {
> +/*
> + * r8a7740 chip has lasting errata on MERAM buffer.
> + * this is work-around for it.
> + * see
> + *	"Media RAM (MERAM)" on r8a7740 documentation
> + */
> +#define MEBUFCNTR	0xFE950098
> +static void r8a7740_meram_workaround(void)
> +{
> +	void __iomem *reg;
> +
> +	reg = ioremap_nocache(MEBUFCNTR, 4);
> +	if (reg) {
> +		iowrite32(0x01600164, reg);
> +		iounmap(reg);
> +	}
> +}
> +
If this exists within the MERAM register space, it should probably be
handled in the MERAM driver itself. If this is all going to go to DT in
the future it will be easy to to node to quirk matching then, but in the
mean time we can match on CPU or machine types.

  reply	other threads:[~2012-05-22  2:56 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 [this message]
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
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=20120522025635.GA22483@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.