All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Price <steven.price@arm.com>
To: alyssa.rosenzweig@collabora.com, dri-devel@lists.freedesktop.org
Cc: airlied@linux.ie, tomeu.vizoso@collabora.com
Subject: Re: [PATCH 8/9] drm/panfrost: Add Mali-G57 "Natt" support
Date: Mon, 14 Feb 2022 16:23:42 +0000	[thread overview]
Message-ID: <e9d3425f-2e26-1bc1-da98-a7836da68d76@arm.com> (raw)
In-Reply-To: <20220211202728.6146-9-alyssa.rosenzweig@collabora.com>

On 11/02/2022 20:27, alyssa.rosenzweig@collabora.com wrote:
> From: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
> 
> Add the features, issues, and GPU ID for Mali-G57, a first-generation
> Valhall GPU. Other first- and second-generation Valhall GPUs should be
> similar.
> 
> Signed-off-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
> ---
>  drivers/gpu/drm/panfrost/panfrost_features.h | 12 ++++++++++++
>  drivers/gpu/drm/panfrost/panfrost_gpu.c      |  2 ++
>  drivers/gpu/drm/panfrost/panfrost_issues.h   |  5 +++++
>  3 files changed, 19 insertions(+)
> 
> diff --git a/drivers/gpu/drm/panfrost/panfrost_features.h b/drivers/gpu/drm/panfrost/panfrost_features.h
> index 1a8bdebc86a3..7ed0cd3ea2d4 100644
> --- a/drivers/gpu/drm/panfrost/panfrost_features.h
> +++ b/drivers/gpu/drm/panfrost/panfrost_features.h
> @@ -106,6 +106,18 @@ enum panfrost_hw_feature {
>  	BIT_ULL(HW_FEATURE_TLS_HASHING) | \
>  	BIT_ULL(HW_FEATURE_3BIT_EXT_RW_L2_MMU_CONFIG))
>  
> +#define hw_features_g57 (\
> +	BIT_ULL(HW_FEATURE_JOBCHAIN_DISAMBIGUATION) | \
> +	BIT_ULL(HW_FEATURE_PWRON_DURING_PWROFF_TRANS) | \
> +	BIT_ULL(HW_FEATURE_XAFFINITY) | \
> +	BIT_ULL(HW_FEATURE_FLUSH_REDUCTION) | \
> +	BIT_ULL(HW_FEATURE_PROTECTED_MODE) | \
> +	BIT_ULL(HW_FEATURE_PROTECTED_DEBUG_MODE) | \
> +	BIT_ULL(HW_FEATURE_COHERENCY_REG) | \
> +	BIT_ULL(HW_FEATURE_AARCH64_MMU) | \
> +	BIT_ULL(HW_FEATURE_IDVS_GROUP_SIZE) | \
> +	BIT_ULL(HW_FEATURE_CLEAN_ONLY_SAFE))
> +
>  static inline bool panfrost_has_hw_feature(struct panfrost_device *pfdev,
>  					   enum panfrost_hw_feature feat)
>  {
> diff --git a/drivers/gpu/drm/panfrost/panfrost_gpu.c b/drivers/gpu/drm/panfrost/panfrost_gpu.c
> index 73e5774f01c1..08d657527099 100644
> --- a/drivers/gpu/drm/panfrost/panfrost_gpu.c
> +++ b/drivers/gpu/drm/panfrost/panfrost_gpu.c
> @@ -201,6 +201,8 @@ static const struct panfrost_model gpu_models[] = {
>  	GPU_MODEL(g52, 0x7002),
>  	GPU_MODEL(g31, 0x7003,
>  		GPU_REV(g31, 1, 0)),
> +
> +	GPU_MODEL(g57, 0x9001),
>  };
>  
>  static void panfrost_gpu_init_features(struct panfrost_device *pfdev)
> diff --git a/drivers/gpu/drm/panfrost/panfrost_issues.h b/drivers/gpu/drm/panfrost/panfrost_issues.h
> index b8865fc9efce..1a0dc7f7f857 100644
> --- a/drivers/gpu/drm/panfrost/panfrost_issues.h
> +++ b/drivers/gpu/drm/panfrost/panfrost_issues.h
> @@ -258,6 +258,11 @@ enum panfrost_hw_issue {
>  
>  #define hw_issues_g76 0
>  
> +#define hw_issues_g57 (\
> +	BIT_ULL(HW_ISSUE_TTRX_2968_TTRX_3162) | \
> +	BIT_ULL(HW_ISSUE_TTRX_3076) | \
> +	BIT_ULL(HW_ISSUE_TTRX_3485))

Do you know whether you have an r0p0 or an r0p1 Natt? Only the r0p0 has
the 3485 issue, and we might be lucky and it's the r0p1 that's "in the
wild".

It would be good to annotate these lists with the hardware revisions
when there is a difference.

Steve

> +
>  static inline bool panfrost_has_hw_issue(const struct panfrost_device *pfdev,
>  					 enum panfrost_hw_issue issue)
>  {


  reply	other threads:[~2022-02-14 16:23 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 20:27 [PATCH 0/9] drm/panfrost: Initial Valhall support alyssa.rosenzweig
2022-02-11 20:27 ` [PATCH 1/9] dt-bindings: Add arm,mali-valhall compatible alyssa.rosenzweig
2022-02-11 20:27   ` alyssa.rosenzweig
2022-02-14 16:23   ` Steven Price
2022-02-14 16:23     ` Steven Price
2022-02-14 16:58     ` Alyssa Rosenzweig
2022-02-14 16:58       ` Alyssa Rosenzweig
2022-02-14 17:38     ` Daniel Stone
2022-02-14 17:38       ` Daniel Stone
2022-02-15 12:17   ` Robin Murphy
2022-02-15 12:17     ` Robin Murphy
2022-02-15 15:22   ` Rob Herring
2022-02-15 15:22     ` Rob Herring
2022-02-11 20:27 ` [PATCH 2/9] drm/panfrost: Handle HW_ISSUE_TTRX_2968_TTRX_3162 alyssa.rosenzweig
2022-02-14 16:23   ` Steven Price
2022-02-11 20:27 ` [PATCH 3/9] drm/panfrost: Constify argument to has_hw_issue alyssa.rosenzweig
2022-02-14 16:23   ` Steven Price
2022-02-11 20:27 ` [PATCH 4/9] drm/panfrost: Handle HW_ISSUE_TTRX_3076 alyssa.rosenzweig
2022-02-14 16:23   ` Steven Price
2022-02-14 17:06     ` Alyssa Rosenzweig
2022-02-16 16:06       ` Steven Price
2022-02-11 20:27 ` [PATCH 5/9] drm/panfrost: Add HW_ISSUE_TTRX_3485 quirk alyssa.rosenzweig
2022-02-14 16:23   ` Steven Price
2022-02-14 17:11     ` Alyssa Rosenzweig
2022-02-11 20:27 ` [PATCH 6/9] drm/panfrost: Add "clean only safe" feature bit alyssa.rosenzweig
2022-02-14 16:23   ` Steven Price
2022-02-14 17:01     ` Alyssa Rosenzweig
2022-02-16 16:06       ` Steven Price
2022-02-11 20:27 ` [PATCH 7/9] drm/panfrost: Don't set L2_MMU_CONFIG quirks alyssa.rosenzweig
2022-02-14 16:23   ` Steven Price
2022-02-11 20:27 ` [PATCH 8/9] drm/panfrost: Add Mali-G57 "Natt" support alyssa.rosenzweig
2022-02-14 16:23   ` Steven Price [this message]
2022-02-14 17:04     ` Alyssa Rosenzweig
2022-02-11 20:27 ` [PATCH 9/9] drm/panfrost: Handle arm,mali-valhall compatible alyssa.rosenzweig
2022-02-14 16:23   ` Steven Price

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=e9d3425f-2e26-1bc1-da98-a7836da68d76@arm.com \
    --to=steven.price@arm.com \
    --cc=airlied@linux.ie \
    --cc=alyssa.rosenzweig@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=tomeu.vizoso@collabora.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 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.