From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: dts: imx6qdl.dtsi: add "arm, shared-override" for pl310
Date: Mon, 13 Jun 2016 11:24:01 +0200 [thread overview]
Message-ID: <1465809841.2313.2.camel@pengutronix.de> (raw)
In-Reply-To: <20160611115733.GM20243@tiger>
Am Samstag, den 11.06.2016, 19:57 +0800 schrieb Shawn Guo:
> + Lucas
>
> On Tue, Jun 07, 2016 at 05:39:25PM +0800, Peter Chen wrote:
> > The imx6 SMP system has the same DMA memory coherency issue [1] with
> > pl310 L2 controller. With this shared override bit set, the customer
> > reports the DMA coherency issue is gone. Besides, I have tested
> > the performance using USB ethernet with/without this bit, it shows
> > no difference.
> >
> > [1] http://patchwork.ozlabs.org/patch/469362/
> >
> > Signed-off-by: Peter Chen <peter.chen@nxp.com>
> > ---
> > arch/arm/boot/dts/imx6qdl.dtsi | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/arm/boot/dts/imx6qdl.dtsi b/arch/arm/boot/dts/imx6qdl.dtsi
> > index ed613eb..30e21ee 100644
> > --- a/arch/arm/boot/dts/imx6qdl.dtsi
> > +++ b/arch/arm/boot/dts/imx6qdl.dtsi
> > @@ -185,6 +185,7 @@
> > cache-level = <2>;
> > arm,tag-latency = <4 2 3>;
> > arm,data-latency = <4 2 3>;
> > + arm,shared-override;
>
> Lucas had an objection to the change [1], considering the case that
> kernel is booted as non-secure.
My objection to this change still stands. Configuring the L2C to be
compliant to the ARMv7 ARM is at the same level as the CPU workarounds
that can not be applied in secure mode. Those must be done in the
firmware, if your firmware doesn't do it it's plain broken.
Regards,
Lucas
next prev parent reply other threads:[~2016-06-13 9:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 9:39 [PATCH 1/1] ARM: dts: imx6qdl.dtsi: add "arm, shared-override" for pl310 Peter Chen
2016-06-11 11:57 ` Shawn Guo
2016-06-13 9:15 ` Peter Chen
2016-06-13 9:24 ` Lucas Stach [this message]
2016-06-13 9:42 ` Peter Chen
2016-06-13 11:14 ` Lucas Stach
2016-06-14 1:30 ` Peter Chen
2016-06-14 10:11 ` Lucas Stach
2016-06-16 1:02 ` Shawn Guo
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=1465809841.2313.2.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--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).