All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Linton <jeremy.linton@arm.com>
To: util-linux@vger.kernel.org
Cc: Jeremy Linton <jeremy.linton@arm.com>
Subject: [PATCH] lscpu: Even more Arm part numbers
Date: Thu,  1 Sep 2022 16:52:30 -0500	[thread overview]
Message-ID: <20220901215230.2543624-1-jeremy.linton@arm.com> (raw)

Arm has published further MIDR/part numbers on
https://developer.arm.com/ip-products/processors/cortex-a.
Some of the new ones have already been merged, so lets
fill in the gaps with A34, A65AE and X1C.

Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
---
 sys-utils/lscpu-arm.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/sys-utils/lscpu-arm.c b/sys-utils/lscpu-arm.c
index ac3703e1e..9222b77ed 100644
--- a/sys-utils/lscpu-arm.c
+++ b/sys-utils/lscpu-arm.c
@@ -64,6 +64,7 @@ static const struct id_part arm_part[] = {
     { 0xc27, "Cortex-M7" },
     { 0xc60, "Cortex-M0+" },
     { 0xd01, "Cortex-A32" },
+    { 0xd02, "Cortex-A34" },
     { 0xd03, "Cortex-A53" },
     { 0xd04, "Cortex-A35" },
     { 0xd05, "Cortex-A55" },
@@ -82,6 +83,7 @@ static const struct id_part arm_part[] = {
     { 0xd40, "Neoverse-V1" },
     { 0xd41, "Cortex-A78" },
     { 0xd42, "Cortex-A78AE" },
+    { 0xd43, "Cortex-A65AE" },
     { 0xd44, "Cortex-X1" },
     { 0xd46, "Cortex-A510" },
     { 0xd47, "Cortex-A710" },
@@ -89,6 +91,7 @@ static const struct id_part arm_part[] = {
     { 0xd49, "Neoverse-N2" },
     { 0xd4a, "Neoverse-E1" },
     { 0xd4b, "Cortex-A78C" },
+    { 0xd4c, "Cortex-X1C" },
     { 0xd4d, "Cortex-A715" },
     { 0xd4e, "Cortex-X3" },
     { -1, "unknown" },
-- 
2.35.3


             reply	other threads:[~2022-09-01 21:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 21:52 Jeremy Linton [this message]
2022-09-02  8:07 ` [PATCH] lscpu: Even more Arm part numbers Karel Zak
  -- strict thread matches above, loose matches on Subject: below --
2020-11-10 16:05 Jeremy Linton
2020-11-13 10:23 ` Karel Zak

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=20220901215230.2543624-1-jeremy.linton@arm.com \
    --to=jeremy.linton@arm.com \
    --cc=util-linux@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.