Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: vitaly prosyak <vprosyak@amd.com>
To: Tim Huang <tim.huang@amd.com>, igt-dev@lists.freedesktop.org
Cc: vitaly.prosyak@amd.com, alexander.deucher@amd.com, jie1zhan@amd.com
Subject: Re: [PATCH i-g-t] lib/amdgpu: add GFX1153 to GFX1150 family
Date: Mon, 30 Dec 2024 11:33:42 -0500	[thread overview]
Message-ID: <b6ee574d-4bc5-4522-b011-25b441ee1164@amd.com> (raw)
In-Reply-To: <20241230065607.3335566-1-tim.huang@amd.com>

The change looks good to me. Please create a Git patch and send it my way, or if you have the necessary access, feel free to merge it directly.

Reviewed-by: Vitaly Prosyak <vitaly.prosyak@amd.com>

On 2024-12-30 01:56, Tim Huang wrote:
> Add GFX1153 to the amdgpu supported chip list.
>
> Signed-off-by: Tim Huang <tim.huang@amd.com>
> ---
>  lib/amdgpu/amd_family.h       | 1 +
>  lib/amdgpu/amd_ip_blocks.c    | 1 +
>  lib/amdgpu/amdgpu_asic_addr.h | 2 ++
>  3 files changed, 4 insertions(+)
>
> diff --git a/lib/amdgpu/amd_family.h b/lib/amdgpu/amd_family.h
> index 54b0ae1d8..60190c639 100644
> --- a/lib/amdgpu/amd_family.h
> +++ b/lib/amdgpu/amd_family.h
> @@ -107,6 +107,7 @@ enum radeon_family {
>  	CHIP_GFX1150,
>  	CHIP_GFX1151,
>  	CHIP_GFX1152,
> +	CHIP_GFX1153,
>  	CHIP_GFX1200,
>  	CHIP_LAST,
>  };
> diff --git a/lib/amdgpu/amd_ip_blocks.c b/lib/amdgpu/amd_ip_blocks.c
> index 980bb9b0b..cc4163bfc 100644
> --- a/lib/amdgpu/amd_ip_blocks.c
> +++ b/lib/amdgpu/amd_ip_blocks.c
> @@ -800,6 +800,7 @@ int setup_amdgpu_ip_blocks(uint32_t major, uint32_t minor, struct amdgpu_gpu_inf
>  		identify_chip(GFX1150);
>  		identify_chip(GFX1151);
>  		identify_chip(GFX1152);
> +		identify_chip(GFX1153);
>  		break;
>  	case FAMILY_GFX1200:
>  		identify_chip(GFX1200);
> diff --git a/lib/amdgpu/amdgpu_asic_addr.h b/lib/amdgpu/amdgpu_asic_addr.h
> index d5579ce4c..63cea1a5d 100644
> --- a/lib/amdgpu/amdgpu_asic_addr.h
> +++ b/lib/amdgpu/amdgpu_asic_addr.h
> @@ -110,6 +110,7 @@
>  #define AMDGPU_GFX1150_RANGE     0x01, 0x40 //# 01 <= x < 64
>  #define AMDGPU_GFX1151_RANGE     0xc0, 0xFF //# 192 <= x < 255
>  #define AMDGPU_GFX1152_RANGE     0x40, 0x50 //# 64 <= x < 80
> +#define AMDGPU_GFX1153_RANGE     0x50, 0xC0 //# 80 <= x < 192
>  #define AMDGPU_GFX1200_RANGE     0x01, 0xFF //# 01 <= x < 255
>  
>  #define AMDGPU_EXPAND_FIX(x) x
> @@ -177,6 +178,7 @@
>  #define ASICREV_IS_GFX1150(r)          ASICREV_IS(r, GFX1150)
>  #define ASICREV_IS_GFX1151(r)          ASICREV_IS(r, GFX1151)
>  #define ASICREV_IS_GFX1152(r)          ASICREV_IS(r, GFX1152)
> +#define ASICREV_IS_GFX1153(r)          ASICREV_IS(r, GFX1153)
>  #define ASICREV_IS_GFX1200(r)          ASICREV_IS(r, GFX1200)
>  
>  #endif // _AMDGPU_ASIC_ADDR_H

      parent reply	other threads:[~2024-12-30 16:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-30  6:56 [PATCH i-g-t] lib/amdgpu: add GFX1153 to GFX1150 family Tim Huang
2024-12-30  7:50 ` ✓ i915.CI.BAT: success for " Patchwork
2024-12-30  7:52 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-30  9:19 ` ✗ Xe.CI.Full: failure " Patchwork
2024-12-30  9:34 ` ✗ i915.CI.Full: " Patchwork
2024-12-30 16:33 ` 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=b6ee574d-4bc5-4522-b011-25b441ee1164@amd.com \
    --to=vprosyak@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jie1zhan@amd.com \
    --cc=tim.huang@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