public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/3] ARM: l2c: add l2c support for RZ/A1
Date: Thu, 16 Feb 2017 17:21:28 +0000	[thread overview]
Message-ID: <20170216172128.GS27312@n2100.armlinux.org.uk> (raw)
In-Reply-To: <CAK8P3a1ri2o4An0svxSG4iSvwTkdpM5jiC=SzBq7mE6TpbdhKQ@mail.gmail.com>

On Thu, Feb 16, 2017 at 05:57:53PM +0100, Arnd Bergmann wrote:
> On Thu, Feb 16, 2017 at 5:44 PM, Russell King - ARM Linux
> <linux@armlinux.org.uk> wrote:
> > On Thu, Feb 16, 2017 at 11:17:39AM -0500, Chris Brandt wrote:
> >> The PL310 in the Renesas RZ/A1 SoC (R7S72100) does not have the sideband
> >> signals connected between the CPU and L2C. According the PL310 TRM,
> >> sideband signals are optional.
> >>
> >> If a PL310 is added to a system, but the sideband signals are not
> >> connected, some Cortex A9 optimizations cannot be used. In particular,
> >> enabling Full Line Zeros in the CA9 without sidebands connected will
> >> crash the system since the CA9 will expect the L2C to perform operations,
> >> yet the L2C never gets the commands.
> >>
> >> This series adds the option to not enable anything in the PL310 that
> >> uses sidebands, and then adds L2C support to the RZ/A1 DT.
> >>
> >> v4:
> >> * changed l2x0_bresp_dis to l2x0_bresp_disable
> >> * changed l2x0_flz_dis to l2x0_flz_disable
> >
> > Looks good, thanks.
> >
> > I'll want to merge patch 1, but I suspect the other two patches need
> > to go through arm-soc, which will cause a problem due to being merged
> > independently...  Arnd?
> 
> I just checked what we have queued up in next/dt for this platform,
> and I'm fairly sure that there are no conflicts, so you can pick up all three
> and add
> 
> Acked-by: Arnd Bergmann <arnd@arndb.de>

Chris, can you put all three in the patch system, preferably with
Arnd's ack for the last two please?

Thanks.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2017-02-16 17:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 16:17 [PATCH v4 0/3] ARM: l2c: add l2c support for RZ/A1 Chris Brandt
2017-02-16 16:17 ` [PATCH v4 1/3] ARM: l2c: allow CA9 optimizations to be disabled Chris Brandt
2017-02-16 16:17 ` [PATCH v4 2/3] ARM: shmobile: r7s72100: Enable L2 cache Chris Brandt
2017-02-16 16:17 ` [PATCH v4 3/3] ARM: dts: r7s72100: add l2 cache Chris Brandt
2017-02-16 16:44 ` [PATCH v4 0/3] ARM: l2c: add l2c support for RZ/A1 Russell King - ARM Linux
2017-02-16 16:57   ` Arnd Bergmann
2017-02-16 17:21     ` Russell King - ARM Linux [this message]
2017-02-16 17:26       ` Chris Brandt
2017-03-08 18:53       ` Chris Brandt
2017-03-08 19:16         ` Russell King - ARM Linux
2017-03-08 19:35           ` Chris Brandt

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=20170216172128.GS27312@n2100.armlinux.org.uk \
    --to=linux@armlinux.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