public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bod@kernel.org>
To: Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
	Abhinav Kumar <abhinav.kumar@linux.dev>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] media: iris: Enable Gen2 HFI on SC7280
Date: Tue, 17 Feb 2026 10:37:38 +0000	[thread overview]
Message-ID: <36e636d9-befb-40fd-b63c-6ae48df61199@kernel.org> (raw)
In-Reply-To: <2f85b131-2167-838c-152a-03be689b0b29@oss.qualcomm.com>

On 17/02/2026 07:40, Dikshita Agarwal wrote:
> Due to these constraints, I think, the only possible way is to extract the
> version from the firmware binary blob itself.

According to the internet machine

MDT::SW_ID
      GEN1 == 0x0b || 0x0c
      GEN2 == 0x24 (or above one assumes)

If you can verify that with the Iris firmware people we should be able 
to parse that data out of the mdt header and reliably differentiate on it.

---
bod

  reply	other threads:[~2026-02-17 10:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09  9:45 [PATCH 0/2] media: qcom: iris: Add Gen2 HFI support for SC7280 Dikshita Agarwal
2026-02-09  9:45 ` [PATCH 1/2] media: iris: Initialize HFI ops after firmware load in core init Dikshita Agarwal
2026-02-09 11:34   ` Bryan O'Donoghue
2026-02-09  9:45 ` [PATCH 2/2] media: iris: Enable Gen2 HFI on SC7280 Dikshita Agarwal
2026-02-09 10:02   ` Konrad Dybcio
2026-02-09 11:34     ` Dikshita Agarwal
2026-02-09 11:36       ` Bryan O'Donoghue
2026-02-09 11:39       ` Konrad Dybcio
2026-02-09 12:35       ` Dmitry Baryshkov
2026-02-12 11:16         ` Dikshita Agarwal
2026-02-12 11:43           ` Konrad Dybcio
2026-02-12 13:05             ` Dikshita Agarwal
2026-02-12 13:27               ` Bryan O'Donoghue
2026-02-12 14:50                 ` Konrad Dybcio
2026-02-13 11:08                 ` Dmitry Baryshkov
2026-02-13 12:04               ` Dmitry Baryshkov
2026-02-16  8:23                 ` Dikshita Agarwal
2026-02-16 12:03                   ` Dmitry Baryshkov
2026-02-16 12:24                     ` Dikshita Agarwal
2026-02-16 14:42                       ` Dmitry Baryshkov
2026-02-17  7:40                 ` Dikshita Agarwal
2026-02-17 10:37                   ` Bryan O'Donoghue [this message]
2026-02-17 12:04                     ` Dmitry Baryshkov
2026-02-17 12:20                   ` Konrad Dybcio
2026-02-20  6:20                     ` Dikshita Agarwal
2026-02-23  1:14                       ` Dmitry Baryshkov
2026-02-17 13:05                   ` Dmitry Baryshkov
2026-02-09 12:33   ` Dmitry Baryshkov

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=36e636d9-befb-40fd-b63c-6ae48df61199@kernel.org \
    --to=bod@kernel.org \
    --cc=abhinav.kumar@linux.dev \
    --cc=dikshita.agarwal@oss.qualcomm.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=vikash.garodia@oss.qualcomm.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