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: [PATCH V3 3/6] arm: cache-l2x0: add support for Aurora L2 cache ctrl
Date: Thu, 6 Sep 2012 14:02:17 +0100	[thread overview]
Message-ID: <20120906130217.GI858@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <50488DB8.1010007@free-electrons.com>

On Thu, Sep 06, 2012 at 12:49:12PM +0100, Gregory CLEMENT wrote:
> On 09/06/2012 01:11 PM, Will Deacon wrote:
> > On Wed, Sep 05, 2012 at 02:44:34PM +0100, Gregory CLEMENT wrote:
> >> Aurora Cache Controller was designed to be compatible with the ARM L2
> >> Cache Controller. It comes with some difference or improvement such
> >> as:
> >> - no cache id part number available through hardware (need to get it
> >>   by the DT).
> >> - always write through mode available.
> >> - two flavors of the controller outer cache and system cache (meaning
> >>   maintenance operations on L1 are broadcasted to the L2 and L2
> >>   performs the same operation).
> >> - in outer cache mode, the cache maintenance operations are improved and
> >>   can be done on a range inside a page and are not limited to a cache
> >>   line.

[...]

> > Reviewed-by: Will Deacon <will.deacon@arm.com>
> > 
> 
> Thanks. I guess you also reviewed patches 1 and 2, don't you?

Well I didn't really read those because they looked fairly boring :)
Boring is good though, so I doubt they're problematic.

> And then where should I push my series?
> 
> Patches 1,2 and 3 depend of ARM subsystem so they should be submitted
> using Russell King's patch state system. Patches 4 and 5 are more soc
> specific and should go to marvell tree and then arm-soc. But patches 4
> and 5 are meaningless if the first patches are not applied. What is the
> good practice?

When I end up in situations like this, I usually prepare a branch for
Russell containing the patches that should go via his tree. Then, send him a
pull request and once he has pulled it, Arnd and Olof can pull the same
branch into arm-soc as a baseline branch. You can then base your other
patches on top of that.

Make sense?

Will

  reply	other threads:[~2012-09-06 13:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05 13:44 [PATCH V3] Add support for Aurora L2 Cache Controller Gregory CLEMENT
2012-09-05 13:44 ` [PATCH V3 1/6] arm: cache-l2x0: make outer_cache_fns a field of l2x0_of_data Gregory CLEMENT
2012-09-09 19:27   ` Jason Cooper
2012-09-15 20:35   ` Russell King - ARM Linux
2012-09-20  6:40     ` Gregory CLEMENT
2012-09-05 13:44 ` [PATCH V3 2/6] arm: cache-l2x0: add an optional register to save/restore Gregory CLEMENT
2012-09-09 19:28   ` Jason Cooper
2012-09-05 13:44 ` [PATCH V3 3/6] arm: cache-l2x0: add support for Aurora L2 cache ctrl Gregory CLEMENT
2012-09-06 11:11   ` Will Deacon
2012-09-06 11:49     ` Gregory CLEMENT
2012-09-06 13:02       ` Will Deacon [this message]
2012-09-09 19:33   ` Jason Cooper
2012-09-15 20:42   ` Russell King - ARM Linux
2012-09-20  7:26     ` Gregory CLEMENT
2012-09-05 13:44 ` [PATCH V3 4/6] arm: mvebu: add L2 cache support Gregory CLEMENT
2012-09-09 19:35   ` Jason Cooper
2012-09-05 13:44 ` [PATCH V3 5/6] arm: mvebu: add Aurora L2 Cache Controller to the DT Gregory CLEMENT
2012-09-09 19:36   ` Jason Cooper
2012-09-05 13:44 ` [PATCH V3 6/6] arm: l2x0: add aurora related properties to OF binding Gregory CLEMENT
2012-09-09 19:37   ` Jason Cooper

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=20120906130217.GI858@mudshark.cambridge.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).