From: Krzysztof Kozlowski <krzk@kernel.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Russell King <linux@armlinux.org.uk>,
Kukjin Kim <kgene@kernel.org>, Rob Herring <robh+dt@kernel.org>,
kernel@collabora.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] ARM: exynos: clear prefetch bits in default l2c_aux_val
Date: Sat, 31 Oct 2020 12:49:48 +0100 [thread overview]
Message-ID: <20201031114948.GA6198@kozik-lap> (raw)
In-Reply-To: <e44b5226f3ad1551459830c678ed183762d8e458.1597061474.git.guillaume.tucker@collabora.com>
On Mon, Aug 10, 2020 at 01:22:08PM +0100, Guillaume Tucker wrote:
> Clear the L310_AUX_CTRL_DATA_PREFETCH and L310_AUX_CTRL_INSTR_PREFETCH
> bits in the l2c_aux_val defaults for Exynos since they can now be set
> using the standard l2c2x0 devicetree bindings.
>
> Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>
> ---
>
> Notes:
> v2: split patch to only clear exynos platform register bits
>
> arch/arm/mach-exynos/exynos.c | 4 ++--
Thanks, applied.
Best regards,
Krzysztof
next prev parent reply other threads:[~2020-10-31 11:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 12:22 [PATCH v2 1/4] ARM: exynos: clear L310_AUX_CTRL_NS_LOCKDOWN in default l2c_aux_val Guillaume Tucker
2020-08-10 12:22 ` [PATCH v2 2/4] ARM: l2c: fix prefetch bits init in L2X0_AUX_CTRL using DT values Guillaume Tucker
2020-08-10 12:22 ` [PATCH v2 3/4] ARM: dts: exynos: add prefetch properties for L2C-310 cache Guillaume Tucker
2020-08-10 12:22 ` [PATCH v2 4/4] ARM: exynos: clear prefetch bits in default l2c_aux_val Guillaume Tucker
2020-10-31 11:49 ` Krzysztof Kozlowski [this message]
2020-09-01 13:34 ` [PATCH v2 1/4] ARM: exynos: clear L310_AUX_CTRL_NS_LOCKDOWN " Guillaume Tucker
2020-09-01 13:45 ` Krzysztof Kozlowski
2020-09-01 13:51 ` Krzysztof Kozlowski
2020-09-01 14:42 ` Guillaume Tucker
2020-09-01 15:25 ` Krzysztof Kozlowski
2020-09-01 17:00 ` Guillaume Tucker
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=20201031114948.GA6198@kozik-lap \
--to=krzk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=guillaume.tucker@collabora.com \
--cc=kernel@collabora.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robh+dt@kernel.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).