From: Anand Gore <anand.gore@broadcom.com>
To: Linux ARM List <linux-arm-kernel@lists.infradead.org>
Cc: kursad.oney@broadcom.com, joel.peshkin@broadcom.com,
florian.fainelli@broadcom.com, dan.beygelman@broadcom.com,
samyon.furman@broadcom.com,
William Zhang <william.zhang@broadcom.com>,
tomer.yacoby@broadcom.com, Anand Gore <anand.gore@broadcom.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>, Russell King <linux@armlinux.org.uk>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org
Subject: [PATCH] ARM: bcmbca: add VFP and NEON fixup for bcm6878 SoC
Date: Fri, 27 May 2022 11:17:48 -0700 [thread overview]
Message-ID: <20220527111742.1.I2da72dc550b9c09aa9b83c1028d00d046833a24a@changeid> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 696 bytes --]
BCM6878 SoC only has VFP and NEON support on core 0. So kernel VPF/NEON
support is disabled in this chip. Add this fixup to manually turn on
VFP/NEON in case userspace app need to access them on core 0.
Signed-off-by: Anand Gore <anand.gore@broadcom.com>
---
arch/arm/mach-bcm/bcmbca.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-bcm/bcmbca.c b/arch/arm/mach-bcm/bcmbca.c
index dbf4d95e824e..60eeb2aa772a 100644
--- a/arch/arm/mach-bcm/bcmbca.c
+++ b/arch/arm/mach-bcm/bcmbca.c
@@ -45,6 +45,7 @@ static void __init bcmbca_neon_fixup(void)
static const char *const bcmbca_match[] __initconst = {
"brcm,bcm6846",
+ "brcm,bcm6878",
NULL
};
--
2.25.1
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4203 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2022-05-27 18:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220527111742.1.I2da72dc550b9c09aa9b83c1028d00d046833a24a@changeid \
--to=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.beygelman@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=joel.peshkin@broadcom.com \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=rjui@broadcom.com \
--cc=samyon.furman@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=tomer.yacoby@broadcom.com \
--cc=william.zhang@broadcom.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).