From: Chengwen Feng <fengchengwen@huawei.com>
To: <thomas@monjalon.net>
Cc: <dev@dpdk.org>
Subject: [PATCH v2] config/arm: add HiSilicon HIP12
Date: Wed, 29 Oct 2025 09:16:26 +0800 [thread overview]
Message-ID: <20251029011626.9298-1-fengchengwen@huawei.com> (raw)
In-Reply-To: <20251028084259.4925-1-fengchengwen@huawei.com>
Adding support for HiSilicon HIP12 platform.
Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
---
config/arm/arm64_hip12_linux_gcc | 17 +++++++++++++++++
config/arm/meson.build | 22 ++++++++++++++++++++++
2 files changed, 39 insertions(+)
create mode 100644 config/arm/arm64_hip12_linux_gcc
---
v2: try to fix meson build error "Expecting eof got rcurl"
diff --git a/config/arm/arm64_hip12_linux_gcc b/config/arm/arm64_hip12_linux_gcc
new file mode 100644
index 0000000000..949093d67b
--- /dev/null
+++ b/config/arm/arm64_hip12_linux_gcc
@@ -0,0 +1,17 @@
+[binaries]
+c = ['ccache', 'aarch64-linux-gnu-gcc']
+cpp = ['ccache', 'aarch64-linux-gnu-g++']
+ar = 'aarch64-linux-gnu-gcc-ar'
+strip = 'aarch64-linux-gnu-strip'
+pkgconfig = 'aarch64-linux-gnu-pkg-config'
+pkg-config = 'aarch64-linux-gnu-pkg-config'
+pcap-config = ''
+
+[host_machine]
+system = 'linux'
+cpu_family = 'aarch64'
+cpu = 'armv8.5-a'
+endian = 'little'
+
+[properties]
+platform = 'hip12'
diff --git a/config/arm/meson.build b/config/arm/meson.build
index ec9e08cb5e..c0aa21b57d 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -255,6 +255,15 @@ implementer_hisilicon = {
['RTE_MAX_LCORE', 1280],
['RTE_MAX_NUMA_NODES', 16]
]
+ },
+ '0xd06': {
+ 'mcpu': 'mcpu_hip12',
+ 'flags': [
+ ['RTE_MACHINE', '"hip12"'],
+ ['RTE_ARM_FEATURE_ATOMICS', true],
+ ['RTE_MAX_LCORE', 1280],
+ ['RTE_MAX_NUMA_NODES', 16]
+ ]
}
}
}
@@ -562,6 +571,13 @@ soc_hip10 = {
'numa': true
}
+soc_hip12 = {
+ 'description': 'HiSilicon HIP12',
+ 'implementer': '0x48',
+ 'part_number': '0xd06',
+ 'numa': true
+}
+
soc_imx = {
'description': 'NXP IMX',
'implementer': '0x41',
@@ -703,6 +719,10 @@ mcpu_defs = {
'march': 'armv8.5-a',
'march_extensions': ['crypto', 'sve']
},
+ 'mcpu_hip12': {
+ 'march': 'armv8.5-a',
+ 'march_extensions': ['crypto', 'sve']
+ },
'mcpu_kunpeng930': {
'march': 'armv8.2-a',
'march_extensions': ['crypto', 'sve']
@@ -758,6 +778,7 @@ graviton2: AWS Graviton2
graviton3: AWS Graviton3
graviton4: AWS Graviton4
hip10: HiSilicon HIP10
+hip12: HiSilicon HIP12
imx: NXP IMX
kunpeng920: HiSilicon Kunpeng 920
kunpeng930: HiSilicon Kunpeng 930
@@ -801,6 +822,7 @@ socs = {
'graviton3': soc_graviton3,
'graviton4': soc_graviton4,
'hip10': soc_hip10,
+ 'hip12': soc_hip12,
'imx': soc_imx,
'kunpeng920': soc_kunpeng920,
'kunpeng930': soc_kunpeng930,
--
2.17.1
next prev parent reply other threads:[~2025-10-29 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 8:42 [PATCH] " Chengwen Feng
2025-10-29 1:16 ` Chengwen Feng [this message]
2025-10-29 2:02 ` [PATCH v2] " lihuisong (C)
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=20251029011626.9298-1-fengchengwen@huawei.com \
--to=fengchengwen@huawei.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).