From: vitaly prosyak <vprosyak@amd.com>
To: Jesse Zhang <jesse.zhang@amd.com>, igt-dev@lists.freedesktop.org
Cc: Vitaly Prosyak <vitaly.prosyak@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Christian Koenig <christian.koenig@amd.com>,
Kamil Konieczny <kamil.konieczny@linux.intel.com>
Subject: Re: [PATCH i-g-t 1/3 V2] lib/amdgpu: add gfx12 family id
Date: Thu, 20 Jun 2024 23:05:22 -0400 [thread overview]
Message-ID: <ce33fe83-afb0-4e6a-9330-9904e5a742b5@amd.com> (raw)
In-Reply-To: <20240621024958.2293940-1-jesse.zhang@amd.com>
Looks good to me.
Reviewed-by: Vitaly Prosyak <vitaly.prosyak@amd.com>
On 2024-06-20 22:49, Jesse Zhang wrote:
> To support gfx12 testing, add its family ID.
> V2: using a unique subject (Kamil)
>
> Signed-off-by: Jesse Zhang <Jesse.Zhang@amd.com>
> ---
> lib/amdgpu/amd_family.h | 1 +
> lib/amdgpu/amd_ip_blocks.c | 3 +++
> lib/amdgpu/amdgpu_asic_addr.h | 3 +++
> 3 files changed, 7 insertions(+)
>
> diff --git a/lib/amdgpu/amd_family.h b/lib/amdgpu/amd_family.h
> index bce2c6c2e..4a5731dbf 100644
> --- a/lib/amdgpu/amd_family.h
> +++ b/lib/amdgpu/amd_family.h
> @@ -106,6 +106,7 @@ enum radeon_family {
> CHIP_GFX1103_R2,
> CHIP_GFX1150,
> CHIP_GFX1151,
> + CHIP_GFX1200,
> CHIP_LAST,
> };
>
> diff --git a/lib/amdgpu/amd_ip_blocks.c b/lib/amdgpu/amd_ip_blocks.c
> index 2ee94105c..ff7e55525 100644
> --- a/lib/amdgpu/amd_ip_blocks.c
> +++ b/lib/amdgpu/amd_ip_blocks.c
> @@ -695,6 +695,9 @@ int setup_amdgpu_ip_blocks(uint32_t major, uint32_t minor, struct amdgpu_gpu_inf
> identify_chip(GFX1150);
> identify_chip(GFX1151);
> break;
> + case FAMILY_GFX1200:
> + identify_chip(GFX1200);
> + break;
> }
> if (!info->name) {
> igt_info("amdgpu: unknown (family_id, chip_external_rev): (%u, %u)\n",
> diff --git a/lib/amdgpu/amdgpu_asic_addr.h b/lib/amdgpu/amdgpu_asic_addr.h
> index cbe02871e..0ecb0b803 100644
> --- a/lib/amdgpu/amdgpu_asic_addr.h
> +++ b/lib/amdgpu/amdgpu_asic_addr.h
> @@ -31,6 +31,7 @@
> #define FAMILY_GFX1036 0x95
> #define FAMILY_GFX1150 0x96
> #define FAMILY_GFX1037 0x97
> +#define FAMILY_GFX1200 0x98
>
> // AMDGPU_FAMILY_IS(familyId, familyName)
> #define FAMILY_IS(f, fn) (f == FAMILY_##fn)
> @@ -108,6 +109,7 @@
> #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_GFX1200_RANGE 0x01, 0xFF //# 01 <= x < 255
>
> #define AMDGPU_EXPAND_FIX(x) x
> #define AMDGPU_RANGE_HELPER(val, min, max) ((val >= min) && (val < max))
> @@ -173,5 +175,6 @@
> #define ASICREV_IS_GFX1103_R2(r) ASICREV_IS(r, GFX1103_R2)
> #define ASICREV_IS_GFX1150(r) ASICREV_IS(r, GFX1150)
> #define ASICREV_IS_GFX1151(r) ASICREV_IS(r, GFX1151)
> +#define ASICREV_IS_GFX1200(r) ASICREV_IS(r, GFX1200)
>
> #endif // _AMDGPU_ASIC_ADDR_H
prev parent reply other threads:[~2024-06-21 3:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 2:49 [PATCH i-g-t 1/3 V2] lib/amdgpu: add gfx12 family id Jesse Zhang
2024-06-21 3:05 ` vitaly prosyak [this message]
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=ce33fe83-afb0-4e6a-9330-9904e5a742b5@amd.com \
--to=vprosyak@amd.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jesse.zhang@amd.com \
--cc=kamil.konieczny@linux.intel.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