linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: Add support for the 16-way L310 L2 cache controller
Date: Thu, 29 Apr 2010 17:20:35 +0100	[thread overview]
Message-ID: <000701cae7b7$e61d45f0$b257d1d0$@deacon@arm.com> (raw)

Hi Jason,

The patch entitled `Add support for the 16-way L310 L2 cache controller'
which you submitted to RMK's patch system appears to perform a 16-way
invalidation even when the ways might not be present. This results in
writes to the reserved bits [15:8] of the invalidate-by-way ctrl register.

You can check the associativity by reading bit 16 of the auxiliary ctrl
register.

Will

             reply	other threads:[~2010-04-29 16:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29 16:20 Will Deacon [this message]
2010-04-29 18:28 ` Add support for the 16-way L310 L2 cache controller Russell King - ARM Linux
     [not found] <3756028016583358140@unknownmsgid>
2010-04-30 17:17 ` Jason McMullan
     [not found] <-5319252541413655868@unknownmsgid>
2010-05-03 16:48 ` Jason McMullan

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='000701cae7b7$e61d45f0$b257d1d0$@deacon@arm.com' \
    --to=will.deacon@arm.com \
    --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).