mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Akhil P Oommen <akhilpo@oss.qualcomm.com>
To: Rob Clark <robin.clark@oss.qualcomm.com>,
	dri-devel@lists.freedesktop.org
Cc: freedreno@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
	Abhinav Kumar <abhinav.kumar@linux.dev>,
	David Airlie <airlied@gmail.com>,
	Dmitry Baryshkov <lumag@kernel.org>,
	Jessica Zhang <jesszhan0024@gmail.com>,
	Konrad Dybcio <konradybcio@kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	Marijn Suijten <marijn.suijten@somainline.org>,
	Sean Paul <sean@poorly.run>, Simona Vetter <simona@ffwll.ch>
Subject: Re: [PATCH 0/2] drm/msm/adreno: Update GPU name format
Date: Tue, 17 Mar 2026 02:25:52 +0530	[thread overview]
Message-ID: <2b416eb0-ec84-425b-a845-3995fb2fda4b@oss.qualcomm.com> (raw)
In-Reply-To: <20260316183436.671482-1-robin.clark@oss.qualcomm.com>

On 3/17/2026 12:04 AM, Rob Clark wrote:
> The "ipv4 style" of formatting the chip_id is less useful after a740
> with the new chip_id format.  Rather than doing dec->hex conversion in
> my head, just switch to using %08x, which is still easy enough to read
> for the old scheme.
> 
> Also, for a8xx update the name after patching in the slice-count.
> 
> This series only changes things for kernel dmesg.
> 
> Rob Clark (2):
>   drm/msm/adreno: Change chip_id format
>   drm/msm/a8xx: Update GPU name with slice_mask
> 
>  drivers/gpu/drm/msm/adreno/a8xx_gpu.c   | 10 ++++++++++
>  drivers/gpu/drm/msm/adreno/adreno_gpu.h |  8 ++------
>  2 files changed, 12 insertions(+), 6 deletions(-)
> 

Reviewed-by: Akhil P Oommen <akhilpo@oss.qualcomm.com>

-Akhil.

      parent reply	other threads:[~2026-03-16 20:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 18:34 Rob Clark
2026-03-16 18:34 ` [PATCH 1/2] drm/msm/adreno: Change chip_id format Rob Clark
2026-03-16 18:50   ` Dmitry Baryshkov
2026-03-16 18:34 ` [PATCH 2/2] drm/msm/a8xx: Update GPU name with slice_mask Rob Clark
2026-03-16 18:51   ` Dmitry Baryshkov
2026-03-16 20:55 ` Akhil P Oommen [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=2b416eb0-ec84-425b-a845-3995fb2fda4b@oss.qualcomm.com \
    --to=akhilpo@oss.qualcomm.com \
    --cc=abhinav.kumar@linux.dev \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=jesszhan0024@gmail.com \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=sean@poorly.run \
    --cc=simona@ffwll.ch \
    /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

all inboxes | Powered by JetHome®