linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	"S, Venkatraman" <svenkatr@ti.com>,
	"Guruswamy, Senthilvadivu" <svadivu@ti.com>
Subject: Re: [PATCH 9/9] omap: id: add feature check for omap1
Date: Tue, 6 Jul 2010 16:14:57 +0300	[thread overview]
Message-ID: <20100706131457.GQ3192@atomide.com> (raw)
In-Reply-To: <4C33275E.4030506@ti.com>

* Nishanth Menon <nm@ti.com> [100706 15:47]:
> On 07/06/2010 07:46 AM, Tony Lindgren wrote:
> >* Nishanth Menon<nm@ti.com>  [100623 05:10]:
> >>add a minimalist feature - l2cache for omap1.
> >>
> >>Signed-off-by: Nishanth Menon<nm@ti.com>
> >>---
> >>  arch/arm/mach-omap1/id.c |    6 ++++++
> >>  1 files changed, 6 insertions(+), 0 deletions(-)
> >>
> >>diff --git a/arch/arm/mach-omap1/id.c b/arch/arm/mach-omap1/id.c
> >>index 91dbb71..b98a17f 100644
> >>--- a/arch/arm/mach-omap1/id.c
> >>+++ b/arch/arm/mach-omap1/id.c
> >>@@ -200,5 +200,11 @@ void __init omap1_check_revision(void)
> >>  	printk(KERN_INFO " revision %i handled as %02xxx id: %08x%08x\n",
> >>  	       die_rev, omap_revision&  0xff, system_serial_low,
> >>  	       system_serial_high);
> >>+
> >>+	/*
> >>+	 * TODO: add a better check feature once we have
> >>+	 * more decent feature check
> >>+	 */
> >>+	omap_features |= OMAP_HAS_L2CACHE;
> >>  }
> >
> >There's no L2 cache on omap1?
> 
> I thought it did, hence added.. am I wrong?

Maybe you're thinking something else.. But for example, 1710 TRM says:

ARM926EJ
L1 32K-byte, four-way set-associative instruction cache
L1 16K-byte, four-way set-associative data cache with write buffer

Then 2430 TRM says:

ARM1136JF-S
32K-byte instructions and 32K-byte data--4-way associative
64-entry instruction and 64-entry data memory management units (MMUs)

So no L2 until 34xx I believe.

Regards,

Tony

  reply	other threads:[~2010-07-06 13:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23  2:16 [PATCH 0/9 v2] introduce generic OMAP SOC features Nishanth Menon
2010-06-23  2:16 ` [PATCH 1/9] omap1: rename check_revision Nishanth Menon
2010-06-23  2:16 ` [PATCH 2/9] omap2/3: id: fix sparse warning Nishanth Menon
2010-06-23  2:16 ` [PATCH 3/9] omap: generic: introduce a single check_revision Nishanth Menon
2010-06-25  9:31   ` Grazvydas Ignotas
2010-06-25 13:18     ` Nishanth Menon
2010-06-23  2:16 ` [PATCH 4/9] omap: improve OMAP3_HAS_FEATURE Nishanth Menon
2010-07-07 12:28   ` Tony Lindgren
2010-07-07 13:15     ` Nishanth Menon
2010-07-07 13:30       ` Tony Lindgren
2010-07-07 13:50         ` Nishanth Menon
2010-07-08  9:24           ` Tony Lindgren
2010-06-23  2:16 ` [PATCH 5/9] omap: introduce OMAP_SHOW_FEATURE Nishanth Menon
2010-06-23  2:16 ` [PATCH 6/9] omap: move generic omap3 features to generic Nishanth Menon
2010-07-07 12:30   ` Tony Lindgren
2010-06-23  2:16 ` [PATCH 7/9] omap: introduce omap4 feature Nishanth Menon
2010-06-23  2:16 ` [PATCH 8/9] omap: introduce omap24xx generic features Nishanth Menon
2010-06-23  2:16 ` [PATCH 9/9] omap: id: add feature check for omap1 Nishanth Menon
2010-07-06 12:46   ` Tony Lindgren
2010-07-06 12:53     ` Nishanth Menon
2010-07-06 13:14       ` Tony Lindgren [this message]
2010-07-06 16:07         ` Nishanth Menon

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=20100706131457.GQ3192@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=svadivu@ti.com \
    --cc=svenkatr@ti.com \
    /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).