From: Tim Huang <tim.huang@amd.com>
To: <igt-dev@lists.freedesktop.org>
Cc: <vitaly.prosyak@amd.com>, <alexander.deucher@amd.com>,
<jie1zhan@amd.com>, Tim Huang <tim.huang@amd.com>
Subject: [PATCH i-g-t 1/2] lib/amdgpu: correct the GFX1150 and GFX1151 IDs range
Date: Wed, 7 Aug 2024 14:33:50 +0800 [thread overview]
Message-ID: <20240807063351.727312-1-tim.huang@amd.com> (raw)
GFX1150 IDs range from 01 to 64 and GFX1151 IDs
range from 192 to 255.
Signed-off-by: Tim Huang <tim.huang@amd.com>
Reviewed-by: Vitaly Prosyak <vitaly.prosyak@amd.com>
---
lib/amdgpu/amdgpu_asic_addr.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/amdgpu/amdgpu_asic_addr.h b/lib/amdgpu/amdgpu_asic_addr.h
index 0ecb0b803..3829b0306 100644
--- a/lib/amdgpu/amdgpu_asic_addr.h
+++ b/lib/amdgpu/amdgpu_asic_addr.h
@@ -107,8 +107,8 @@
#define AMDGPU_GFX1102_RANGE 0x10, 0x20 //# 16 <= x < 32
#define AMDGPU_GFX1103_R1_RANGE 0x01, 0x80 //# 1 <= x < 128
#define AMDGPU_GFX1103_R2_RANGE 0x80, 0xFF //# 128 <= x < max
-#define AMDGPU_GFX1150_RANGE 0x01, 0xc0 //# 01 <= x < c0
-#define AMDGPU_GFX1151_RANGE 0xc1, 0xFF //# c1 <= x < 255
+#define AMDGPU_GFX1150_RANGE 0x01, 0x40 //# 01 <= x < 64
+#define AMDGPU_GFX1151_RANGE 0xc0, 0xFF //# 192 <= x < 255
#define AMDGPU_GFX1200_RANGE 0x01, 0xFF //# 01 <= x < 255
#define AMDGPU_EXPAND_FIX(x) x
--
2.43.0
next reply other threads:[~2024-08-07 6:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 6:33 Tim Huang [this message]
2024-08-07 6:33 ` [PATCH i-g-t 2/2] lib/amdgpu: add GFX1152 to GFX1150 family Tim Huang
2024-08-07 8:51 ` ✓ CI.xeBAT: success for series starting with [i-g-t,1/2] lib/amdgpu: correct the GFX1150 and GFX1151 IDs range Patchwork
2024-08-07 8:52 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-08-07 9:52 ` ✗ CI.xeFULL: " Patchwork
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=20240807063351.727312-1-tim.huang@amd.com \
--to=tim.huang@amd.com \
--cc=alexander.deucher@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jie1zhan@amd.com \
--cc=vitaly.prosyak@amd.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