From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: L2 : Errata 588369: Clean & Invalidate do not invalidate clean lines
Date: Mon, 11 Jan 2010 14:45:05 +0000 [thread overview]
Message-ID: <20100111144505.GA4109@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1263220628.6305.44.camel@pc1117.cambridge.arm.com>
On Mon, Jan 11, 2010 at 02:37:08PM +0000, Catalin Marinas wrote:
> On Mon, 2009-12-21 at 10:09 +0000, Santosh Shilimkar wrote:
> > @@ -139,7 +184,12 @@ static void l2x0_flush_range(unsigned long start, unsigned long end)
> > spin_lock_irqsave(&l2x0_lock, flags);
> > }
> > }
> > +#ifdef CONFIG_PL310_ERRATA_588369
> > + cache_wait(base + L2X0_CLEAN_LINE_PA, 1);
> > + cache_wait(base + L2X0_INV_LINE_PA, 1);
> > +#else
> > cache_wait(base + L2X0_CLEAN_INV_LINE_PA, 1);
> > +#endif
>
> I don't think we need to way on two separate registers here. AFAICT, bit
> 1 of those registers is shared for all the operations.
>
> As a general comment, maybe an inline function called something like
> wait_writel(before/after) would be better than a lot of ifdefs in the
> code, especially if one has a different workaround other than using TI's
> secure monitor.
Since the bit is shared between all 'R7' registers, the ifdef above makes
no sense. We can just wait on any R7 register - I suggest that bit of
code is left as-is.
next prev parent reply other threads:[~2010-01-11 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 10:09 [PATCH v3] ARM: L2 : Errata 588369: Clean & Invalidate do not invalidate clean lines Santosh Shilimkar
2010-01-07 7:44 ` Shilimkar, Santosh
2010-01-11 14:37 ` Catalin Marinas
2010-01-11 14:45 ` Russell King - ARM Linux [this message]
2010-01-11 15:21 ` Shilimkar, Santosh
2010-01-11 15:18 ` Shilimkar, Santosh
2010-01-11 15:23 ` Russell King - ARM Linux
2010-01-11 15:29 ` Shilimkar, Santosh
2010-01-12 7:41 ` Shilimkar, Santosh
2010-01-11 16:26 ` [PATCH v3] ARM: L2 : Errata 588369: Clean & Invalidate do notinvalidate " Catalin Marinas
2010-01-11 16:29 ` Russell King - ARM Linux
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=20100111144505.GA4109@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).