From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Add ARCH_HAS_L2X0 and make CACHE_L2X0 config depend on that
Date: Sun, 13 Jun 2010 06:16:26 +0100 [thread overview]
Message-ID: <20100613051625.GA7248@trinity.fluff.org> (raw)
In-Reply-To: <1276279087.31800.6.camel@c-dwalke-linux.qualcomm.com>
On Fri, Jun 11, 2010 at 10:58:07AM -0700, Daniel Walker wrote:
> On Fri, 2010-06-11 at 11:03 -0500, Olof Johansson wrote:
>
> > diff --git a/arch/arm/mm/Kconfig b/arch/arm/mm/Kconfig
> > index 346ae14..419b957 100644
> > --- a/arch/arm/mm/Kconfig
> > +++ b/arch/arm/mm/Kconfig
> > @@ -759,11 +759,13 @@ config CACHE_FEROCEON_L2_WRITETHROUGH
> > Say Y here to use the Feroceon L2 cache in writethrough mode.
> > Unless you specifically require this, say N for writeback mode.
> >
> > +config ARCH_HAS_L2X0
> > + bool
> > + default n
> > +
>
> I made a similar change not too long ago, but Russell wanted the define
> to be HAVE_CACHE_L2X0 ..
possibly, I was thinking ARM_L2X0 would also be an option, since if I
remeber correctly it is selecting the driver not the availability of
it.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2010-06-13 5:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6fqujhaev78923q90va>
2010-06-11 16:03 ` [PATCH] ARM: Add ARCH_HAS_L2X0 and make CACHE_L2X0 config depend on that Olof Johansson
2010-06-11 17:58 ` Daniel Walker
2010-06-12 4:13 ` [PATCH v2] ARM: Add HAVE_CACHE_L2X0 Olof Johansson
2010-06-13 5:16 ` Ben Dooks [this message]
2010-06-14 14:59 ` [PATCH] ARM: Add ARCH_HAS_L2X0 and make CACHE_L2X0 config depend on that Olof Johansson
2010-06-16 3:43 ` Eric Miao
2010-06-16 14:13 ` Olof Johansson
2010-06-16 14:22 ` Eric Miao
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=20100613051625.GA7248@trinity.fluff.org \
--to=ben-linux@fluff.org \
--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).