From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: "Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Daniel González Cabanelas" <dgcbueu@gmail.com>,
"Álvaro Fernández Rojas" <noltari@gmail.com>
Subject: Re: [PATCH v5 4/4] mips: bmips: enable RAC on BMIPS4350
Date: Tue, 11 Jun 2024 10:47:16 +0200 [thread overview]
Message-ID: <ZmgPFLSCxjed2EGZ@alpha.franken.de> (raw)
In-Reply-To: <20240511130349.23409-5-ansuelsmth@gmail.com>
On Sat, May 11, 2024 at 03:03:48PM +0200, Christian Marangi wrote:
> From: Daniel González Cabanelas <dgcbueu@gmail.com>
>
> The data RAC is left disabled by the bootloader in some SoCs, at least in
> the core it boots from.
> Enabling this feature increases the performance up to +30% depending on the
> task.
>
> Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
> [ rework code and reduce code duplication ]
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> Acked-by: Florian Fainelli <florian.fainelli@broadcom.com>
> ---
> arch/mips/kernel/smp-bmips.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/arch/mips/kernel/smp-bmips.c b/arch/mips/kernel/smp-bmips.c
> index 20e2fb10022d..52324738cbb3 100644
> --- a/arch/mips/kernel/smp-bmips.c
> +++ b/arch/mips/kernel/smp-bmips.c
> @@ -626,6 +626,23 @@ void bmips_cpu_setup(void)
> __raw_readl(cbr + BMIPS_RAC_ADDRESS_RANGE);
> break;
>
> + case CPU_BMIPS4350:
> + u32 rac_addr = BMIPS_RAC_CONFIG_1;
my gcc 10.2.1 doesn't like the declaration here:
/local/tbogendoerfer/korg/linux/arch/mips/kernel/smp-bmips.c:630:3: error: a label can only be part of a statement and a declaration is not a statement
630 | u32 rac_addr = BMIPS_RAC_CONFIG_1;
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2024-06-11 8:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 13:03 [PATCH v5 0/4] mips: bmips: improve handling of RAC and CBR addr Christian Marangi
2024-05-11 13:03 ` [PATCH v5 1/4] mips: bmips: rework and cache CBR addr handling Christian Marangi
2024-06-11 8:44 ` Thomas Bogendoerfer
2024-06-11 11:37 ` Christian Marangi
2024-06-11 8:45 ` Thomas Bogendoerfer
2024-05-11 13:03 ` [PATCH v5 2/4] dt-bindings: mips: brcm: Document brcm,bmips-cbr-reg property Christian Marangi
2024-05-13 14:22 ` Rob Herring (Arm)
2024-05-13 15:25 ` Florian Fainelli
2024-05-11 13:03 ` [PATCH v5 3/4] mips: bmips: setup: make CBR address configurable Christian Marangi
2024-05-11 13:03 ` [PATCH v5 4/4] mips: bmips: enable RAC on BMIPS4350 Christian Marangi
2024-06-11 8:47 ` Thomas Bogendoerfer [this message]
2024-06-11 11:37 ` Christian Marangi
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=ZmgPFLSCxjed2EGZ@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=ansuelsmth@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dgcbueu@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=robh@kernel.org \
--cc=zajec5@gmail.com \
/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).