mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>
Cc: Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
	Abhinav Kumar <abhinav.kumar@linux.dev>,
	Bryan O'Donoghue <bod@kernel.org>,
	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 v7 7/8] media: qcom: iris: split firmware_data from raw platform data
Date: Wed, 18 Mar 2026 16:03:07 +0530	[thread overview]
Message-ID: <eff4fb4b-d857-5c0b-2285-946806e8e4cf@oss.qualcomm.com> (raw)
In-Reply-To: <yhkio67g2ka222lq72w5cmftczdsiugws3ykpcxuhdrhu54oh5@gjazz3j5lci4>



On 3/18/2026 3:59 PM, Dmitry Baryshkov wrote:
> On Wed, Mar 18, 2026 at 02:35:30PM +0530, Dikshita Agarwal wrote:
>>
>>
>> On 3/17/2026 12:24 AM, Dmitry Baryshkov wrote:
>>> Having firmware-related fields in platform data results in the tying
>>> platform data to the HFI firmware data rather than the actual hardware.
>>> For example, SM8450 uses Gen2 firmware, so currently its platform data
>>> should be placed next to the other gen2 platforms, although it has the
>>> VPU2.0 core, similar to the one found on SM8250 and SC7280 and so the
>>> hardware-specific platform data is also close to those devices.
>>>
>>> Split firmware data to a separate struct, separating hardware-related
>>> data from the firmware interfaces.
>>>
>>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>>> ---
>>>  drivers/media/platform/qcom/iris/iris_buffer.c     |  82 +++----
>>>  drivers/media/platform/qcom/iris/iris_core.h       |   2 +
>>>  drivers/media/platform/qcom/iris/iris_ctrls.c      |   8 +-
>>>  .../platform/qcom/iris/iris_hfi_gen1_command.c     |   8 +-
>>>  .../platform/qcom/iris/iris_hfi_gen2_command.c     |  66 +++---
>>>  .../platform/qcom/iris/iris_platform_common.h      |  82 ++++---
>>>  .../media/platform/qcom/iris/iris_platform_gen1.c  |  67 +++---
>>>  .../media/platform/qcom/iris/iris_platform_gen2.c  | 246 ++++-----------------
>>>  drivers/media/platform/qcom/iris/iris_probe.c      |   3 +-
>>>  drivers/media/platform/qcom/iris/iris_vidc.c       |  10 +-
>>>  10 files changed, 205 insertions(+), 369 deletions(-)
>>>
>>
>> <snip>
>>
>>> -struct iris_platform_data {
>>> +struct iris_firmware_data {
>>>  	void (*init_hfi_ops)(struct iris_core *core);
>>> -	u32 (*get_vpu_buffer_size)(struct iris_inst *inst, enum iris_buffer_type buffer_type);
>>> -	const struct vpu_ops *vpu_ops;
>>> -	const struct icc_info *icc_tbl;
>>> -	unsigned int icc_tbl_size;
>>> -	const struct bw_info *bw_tbl_dec;
>>> -	unsigned int bw_tbl_dec_size;
>>> -	const char * const *pmdomain_tbl;
>>> -	unsigned int pmdomain_tbl_size;
>>> -	const char * const *opp_pd_tbl;
>>> -	unsigned int opp_pd_tbl_size;
>>> -	const struct platform_clk_data *clk_tbl;
>>> -	const char * const *opp_clk_tbl;
>>> -	unsigned int clk_tbl_size;
>>> -	const char * const *clk_rst_tbl;
>>> -	unsigned int clk_rst_tbl_size;
>>> -	const char * const *controller_rst_tbl;
>>> -	unsigned int controller_rst_tbl_size;
>>> -	u64 dma_mask;
>>> -	const char *fwname;
>>> -	struct iris_fmt *inst_iris_fmts;
>>> -	u32 inst_iris_fmts_size;
>>> -	struct platform_inst_caps *inst_caps;
>>> +
>>>  	const struct platform_inst_fw_cap *inst_fw_caps_dec;
>>>  	u32 inst_fw_caps_dec_size;
>>>  	const struct platform_inst_fw_cap *inst_fw_caps_enc;
>>>  	u32 inst_fw_caps_enc_size;
>>> -	const struct tz_cp_config *tz_cp_config_data;
>>> -	u32 tz_cp_config_data_size;
>>> -	u32 core_arch;
>>
>> This can also be tied to firmware data as this is required to be set for
>> Gen2 only and is 0 for Gen1.
> 
> Will it differ between platforms?

Nope, same for all platforms with HFI Gen2.

Thanks,
Dikshita
> 

  reply	other threads:[~2026-03-18 10:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 18:54 [PATCH v7 0/8] media: qcom: iris: rework platform data handling Dmitry Baryshkov
2026-03-16 18:54 ` [PATCH v7 1/8] media: qcom: iris: drop pas_id from the iris_platform_data struct Dmitry Baryshkov
2026-03-18 11:01   ` Vikash Garodia
2026-03-16 18:54 ` [PATCH v7 2/8] media: qcom: iris: use common set_preset_registers function Dmitry Baryshkov
2026-03-18 11:01   ` Vikash Garodia
2026-03-16 18:54 ` [PATCH v7 3/8] media: qcom: iris: don't use function indirection in gen2-specific code Dmitry Baryshkov
2026-03-18 11:03   ` Vikash Garodia
2026-03-16 18:54 ` [PATCH v7 4/8] media: qcom: iris: split HFI session ops from core ops Dmitry Baryshkov
2026-03-18 11:31   ` Vikash Garodia
2026-03-16 18:54 ` [PATCH v7 5/8] media: qcom: iris: merge hfi_response_ops and hfi_command_ops Dmitry Baryshkov
2026-03-18 11:38   ` Vikash Garodia
2026-03-16 18:54 ` [PATCH v7 6/8] media: qcom: iris: move get_instance to iris_hfi_sys_ops Dmitry Baryshkov
2026-03-18 11:39   ` Vikash Garodia
2026-03-16 18:54 ` [PATCH v7 7/8] media: qcom: iris: split firmware_data from raw platform data Dmitry Baryshkov
2026-03-18  9:05   ` Dikshita Agarwal
2026-03-18 10:29     ` Dmitry Baryshkov
2026-03-18 10:33       ` Dikshita Agarwal [this message]
2026-03-18 10:40         ` Dmitry Baryshkov
2026-03-18 10:42           ` Dikshita Agarwal
2026-03-18 13:42             ` Dmitry Baryshkov
2026-03-16 18:54 ` [PATCH v7 8/8] media: qcom: iris: split platform data from firmware data Dmitry Baryshkov
2026-03-18 10:26   ` Vikash Garodia
2026-03-18 13:52   ` Vikash Garodia

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=eff4fb4b-d857-5c0b-2285-946806e8e4cf@oss.qualcomm.com \
    --to=dikshita.agarwal@oss.qualcomm.com \
    --cc=abhinav.kumar@linux.dev \
    --cc=bod@kernel.org \
    --cc=dmitry.baryshkov@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

all inboxes | Powered by JetHome®