From: Russell King - ARM Linux <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>
To: Chris Brandt <chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
Cc: Simon Horman
<horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>,
Magnus Damm <magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Geert Uytterhoeven
<geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Brad Mouring <brad.mouring-acOepvfBmUk@public.gmane.org>,
Andrey Smirnov
<andrew.smirnov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
Richard Cochran
<rcochran-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v4 0/3] ARM: l2c: add l2c support for RZ/A1
Date: Thu, 16 Feb 2017 16:44:24 +0000 [thread overview]
Message-ID: <20170216164424.GR27312@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20170216161742.29320-1-chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
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?
--
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.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-02-16 16:44 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
[not found] ` <20170216161742.29320-1-chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org>
2017-02-16 16:44 ` Russell King - ARM Linux [this message]
2017-02-16 16:57 ` [PATCH v4 0/3] ARM: l2c: add l2c support for RZ/A1 Arnd Bergmann
2017-02-16 17:21 ` Russell King - ARM Linux
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=20170216164424.GR27312@n2100.armlinux.org.uk \
--to=linux-i+ivw8tiwo2tmtq+vha3yw@public.gmane.org \
--cc=andrew.smirnov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=brad.mouring-acOepvfBmUk@public.gmane.org \
--cc=chris.brandt-zM6kxYcvzFBBDgjK7y7TUQ@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org \
--cc=horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=rcochran-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).