From: Tom Rini <trini@konsulko.com>
To: Philip Oberfichtner <pro@denx.de>
Cc: u-boot@lists.denx.de, Stefano Babic <sbabic@denx.de>,
Marek Vasut <marex@denx.de>,
Christoph Niedermaier <cniedermaier@dh-electronics.com>,
Bharat Gooty <bharat.gooty@broadcom.com>,
Dzmitry Sankouski <dsankouski@gmail.com>,
Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>,
Sean Anderson <sean.anderson@seco.com>, Stefan Roese <sr@denx.de>
Subject: Re: [PATCH v6 2/3] ARM: cache: Allow SPL to build cache-pl310.c
Date: Fri, 2 Sep 2022 09:00:20 -0400 [thread overview]
Message-ID: <20220902130020.GF7942@bill-the-cat> (raw)
In-Reply-To: <20220817130714.3487965-3-pro@denx.de>
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
On Wed, Aug 17, 2022 at 03:07:13PM +0200, Philip Oberfichtner wrote:
> Introduce the new Kconfig symbol CONFIG_SPL_SYS_L2_PL310 to allow the
> SPL to build cache-pl310.c.
>
> Before this commit, the SPL could enable the PL310 L2 cache [1], but the
> cache maintenance functions from cache-pl310.c were only useable for
> non-SPL builds.
>
> After enabling the cache one must be able to flush it, too. Thus this
> commit allows cache-pl310.c to be included in the SPL build.
>
> [1] See for example arch/arm/mach-imx/cache.c: v7_outer_cache_enable()
>
> Signed-off-by: Philip Oberfichtner <pro@denx.de>
Applied to u-boot/next, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-09-02 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 13:07 [PATCH v6 0/3] ARM: imx6: dh-imx6: Enable d-cache early in SPL Philip Oberfichtner
2022-08-17 13:07 ` [PATCH v6 1/3] Convert CONFIG_SYS_L2_PL310 to Kconfig Philip Oberfichtner
2022-09-02 13:00 ` Tom Rini
2022-08-17 13:07 ` [PATCH v6 2/3] ARM: cache: Allow SPL to build cache-pl310.c Philip Oberfichtner
2022-09-02 13:00 ` Tom Rini [this message]
2022-08-17 13:07 ` [PATCH v6 3/3] ARM: imx6: dh-imx6: Enable d-cache early in SPL Philip Oberfichtner
2022-09-02 13:00 ` Tom Rini
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=20220902130020.GF7942@bill-the-cat \
--to=trini@konsulko.com \
--cc=bharat.gooty@broadcom.com \
--cc=cniedermaier@dh-electronics.com \
--cc=dsankouski@gmail.com \
--cc=marex@denx.de \
--cc=pro@denx.de \
--cc=rayagonda.kokatanur@broadcom.com \
--cc=sbabic@denx.de \
--cc=sean.anderson@seco.com \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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