linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jordan Crouse <jcrouse@codeaurora.org>
To: Sharat Masetty <smasetty@codeaurora.org>
Cc: freedreno@lists.freedesktop.org, dri-devel@freedesktop.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] drm: msm: Add 618 gpu to the adreno gpu list
Date: Thu, 23 Jan 2020 08:58:17 -0700	[thread overview]
Message-ID: <20200123155817.GA20380@jcrouse1-lnx.qualcomm.com> (raw)
In-Reply-To: <1579763945-10478-1-git-send-email-smasetty@codeaurora.org>

On Thu, Jan 23, 2020 at 12:49:03PM +0530, Sharat Masetty wrote:
> This patch adds Adreno 618 entry and its associated properties
> to the gpulist entries.
> 
> Signed-off-by: Sharat Masetty <smasetty@codeaurora.org>

I'm extremely confused - these have been in linux-next for weeks. Why are you
sending them out again?

Jordan

> ---
>  drivers/gpu/drm/msm/adreno/adreno_device.c | 11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> diff --git a/drivers/gpu/drm/msm/adreno/adreno_device.c b/drivers/gpu/drm/msm/adreno/adreno_device.c
> index fbbdf86..cb3a6e5 100644
> --- a/drivers/gpu/drm/msm/adreno/adreno_device.c
> +++ b/drivers/gpu/drm/msm/adreno/adreno_device.c
> @@ -167,6 +167,17 @@
>  		.init = a5xx_gpu_init,
>  		.zapfw = "a540_zap.mdt",
>  	}, {
> +		.rev = ADRENO_REV(6, 1, 8, ANY_ID),
> +		.revn = 618,
> +		.name = "A618",
> +		.fw = {
> +			[ADRENO_FW_SQE] = "a630_sqe.fw",
> +			[ADRENO_FW_GMU] = "a630_gmu.bin",
> +		},
> +		.gmem = SZ_512K,
> +		.inactive_period = DRM_MSM_INACTIVE_PERIOD,
> +		.init = a6xx_gpu_init,
> +	}, {
>  		.rev = ADRENO_REV(6, 3, 0, ANY_ID),
>  		.revn = 630,
>  		.name = "A630",
> -- 
> 1.9.1
> 

-- 
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

      parent reply	other threads:[~2020-01-23 15:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23  7:19 [PATCH v2 1/3] drm: msm: Add 618 gpu to the adreno gpu list Sharat Masetty
2020-01-23  7:19 ` [PATCH v2 2/3] drm: msm: a6xx: Add support for A618 Sharat Masetty
2020-02-04  0:21   ` John Stultz
2020-02-04  0:40     ` [Freedreno] " Rob Clark
2020-02-04 16:34       ` Jordan Crouse
2020-01-23  7:19 ` [PATCH v2 3/3] drm: msm: a6xx: Dump GBIF registers, debugbus in gpu state Sharat Masetty
2020-01-23 15:58 ` Jordan Crouse [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=20200123155817.GA20380@jcrouse1-lnx.qualcomm.com \
    --to=jcrouse@codeaurora.org \
    --cc=dri-devel@freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smasetty@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).