From: Vikash Garodia <quic_vgarodia@quicinc.com>
To: <neil.armstrong@linaro.org>,
Dikshita Agarwal <quic_dikshita@quicinc.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: <linux-media@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Bryan O'Donoghue" <bryan.odonoghue@linaro.org>
Subject: Re: [PATCH v4 6/6] media: platform: qcom/iris: add sm8650 support
Date: Thu, 10 Apr 2025 14:43:00 +0530 [thread overview]
Message-ID: <8cade183-72ac-eac1-1a57-a9db37657fca@quicinc.com> (raw)
In-Reply-To: <1550c870-188e-4b41-b17c-2009cda41ffc@linaro.org>
On 4/10/2025 2:31 PM, Neil Armstrong wrote:
> On 09/04/2025 18:57, Vikash Garodia wrote:
>> Hi Neil,
>>
>> On 4/9/2025 8:08 PM, Neil Armstrong wrote:
>>> Add support for the SM8650 platform by re-using the SM8550
>>> definitions and using the vpu33 ops.
>>>
>>> The SM8650/vpu33 requires more reset lines, but the H.264
>>> decoder capabilities are identical.
>>>
>>> Tested-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org> # x1e Dell
>>> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
>>> ---
>>> .../platform/qcom/iris/iris_platform_common.h | 1 +
>>> .../platform/qcom/iris/iris_platform_sm8550.c | 64 ++++++++++++++++++++++
>>> drivers/media/platform/qcom/iris/iris_probe.c | 4 ++
>>> 3 files changed, 69 insertions(+)
>>>
>>> diff --git a/drivers/media/platform/qcom/iris/iris_platform_common.h
>>> b/drivers/media/platform/qcom/iris/iris_platform_common.h
>>> index
>>> fdd40fd80178c4c66b37e392d07a0a62f492f108..6bc3a7975b04d612f6c89206eae95dac678695fc 100644
>>> --- a/drivers/media/platform/qcom/iris/iris_platform_common.h
>>> +++ b/drivers/media/platform/qcom/iris/iris_platform_common.h
>>> @@ -35,6 +35,7 @@ enum pipe_type {
>>> extern struct iris_platform_data sm8250_data;
>>> extern struct iris_platform_data sm8550_data;
>>> +extern struct iris_platform_data sm8650_data;
>>> enum platform_clk_type {
>>> IRIS_AXI_CLK,
>>> diff --git a/drivers/media/platform/qcom/iris/iris_platform_sm8550.c
>>> b/drivers/media/platform/qcom/iris/iris_platform_sm8550.c
>>> index
>>> 35d278996c430f2856d0fe59586930061a271c3e..d0f8fa960d53367023e41bc5807ba3f8beae2efc 100644
>>> --- a/drivers/media/platform/qcom/iris/iris_platform_sm8550.c
>>> +++ b/drivers/media/platform/qcom/iris/iris_platform_sm8550.c
>>> @@ -144,6 +144,10 @@ static const struct icc_info sm8550_icc_table[] = {
>>> static const char * const sm8550_clk_reset_table[] = { "bus" };
>>> +static const char * const sm8650_clk_reset_table[] = { "bus", "core" };
>>> +
>>> +static const char * const sm8650_controller_reset_table[] = { "xo" };
>>> +
>>> static const struct bw_info sm8550_bw_table_dec[] = {
>>> { ((4096 * 2160) / 256) * 60, 1608000 },
>>> { ((4096 * 2160) / 256) * 30, 826000 },
>>> @@ -264,3 +268,63 @@ struct iris_platform_data sm8550_data = {
>>> .dec_op_int_buf_tbl = sm8550_dec_op_int_buf_tbl,
>>> .dec_op_int_buf_tbl_size = ARRAY_SIZE(sm8550_dec_op_int_buf_tbl),
>>> };
>>> +
>>> +/*
>>> + * Shares most of SM8550 data except:
>>> + * - vpu_ops to iris_vpu33_ops
>>> + * - clk_rst_tbl to sm8650_clk_reset_table
>>> + * - controller_rst_tbl to sm8650_controller_reset_table
>>> + * - fwname to "qcom/vpu/vpu33_p4.mbn"
>>> + */
>>> +struct iris_platform_data sm8650_data = {
>>> + .get_instance = iris_hfi_gen2_get_instance,
>>> + .init_hfi_command_ops = iris_hfi_gen2_command_ops_init,
>>> + .init_hfi_response_ops = iris_hfi_gen2_response_ops_init,
>>> + .vpu_ops = &iris_vpu33_ops,
>>> + .set_preset_registers = iris_set_sm8550_preset_registers,
>>> + .icc_tbl = sm8550_icc_table,
>>> + .icc_tbl_size = ARRAY_SIZE(sm8550_icc_table),
>>> + .clk_rst_tbl = sm8650_clk_reset_table,
>>> + .clk_rst_tbl_size = ARRAY_SIZE(sm8650_clk_reset_table),
>>> + .controller_rst_tbl = sm8650_controller_reset_table,
>>> + .controller_rst_tbl_size = ARRAY_SIZE(sm8650_controller_reset_table),
>>> + .bw_tbl_dec = sm8550_bw_table_dec,
>>> + .bw_tbl_dec_size = ARRAY_SIZE(sm8550_bw_table_dec),
>>> + .pmdomain_tbl = sm8550_pmdomain_table,
>>> + .pmdomain_tbl_size = ARRAY_SIZE(sm8550_pmdomain_table),
>>> + .opp_pd_tbl = sm8550_opp_pd_table,
>>> + .opp_pd_tbl_size = ARRAY_SIZE(sm8550_opp_pd_table),
>>> + .clk_tbl = sm8550_clk_table,
>>> + .clk_tbl_size = ARRAY_SIZE(sm8550_clk_table),
>>> + /* Upper bound of DMA address range */
>>> + .dma_mask = 0xe0000000 - 1,
>>> + .fwname = "qcom/vpu/vpu33_p4.mbn",
>>> + .pas_id = IRIS_PAS_ID,
>>> + .inst_caps = &platform_inst_cap_sm8550,
>>> + .inst_fw_caps = inst_fw_cap_sm8550,
>>> + .inst_fw_caps_size = ARRAY_SIZE(inst_fw_cap_sm8550),
>>> + .tz_cp_config_data = &tz_cp_config_sm8550,
>>> + .core_arch = VIDEO_ARCH_LX,
>>> + .hw_response_timeout = HW_RESPONSE_TIMEOUT_VALUE,
>>> + .ubwc_config = &ubwc_config_sm8550,
>>> + .num_vpp_pipe = 4,
>>> + .max_session_count = 16,
>>> + .max_core_mbpf = ((8192 * 4352) / 256) * 2,
>>> + .input_config_params =
>>> + sm8550_vdec_input_config_params,
>>> + .input_config_params_size =
>>> + ARRAY_SIZE(sm8550_vdec_input_config_params),
>>> + .output_config_params =
>>> + sm8550_vdec_output_config_params,
>>> + .output_config_params_size =
>>> + ARRAY_SIZE(sm8550_vdec_output_config_params),
>>> + .dec_input_prop = sm8550_vdec_subscribe_input_properties,
>>> + .dec_input_prop_size = ARRAY_SIZE(sm8550_vdec_subscribe_input_properties),
>>> + .dec_output_prop = sm8550_vdec_subscribe_output_properties,
>>> + .dec_output_prop_size =
>>> ARRAY_SIZE(sm8550_vdec_subscribe_output_properties),
>>> +
>>> + .dec_ip_int_buf_tbl = sm8550_dec_ip_int_buf_tbl,
>>> + .dec_ip_int_buf_tbl_size = ARRAY_SIZE(sm8550_dec_ip_int_buf_tbl),
>>> + .dec_op_int_buf_tbl = sm8550_dec_op_int_buf_tbl,
>>> + .dec_op_int_buf_tbl_size = ARRAY_SIZE(sm8550_dec_op_int_buf_tbl),
>>> +};
>> While i was extending the data for QCS8300 (one another iris-v3 variant), i
>> realize that this file iris_platform_sm8550.c is getting dumped with all SOC
>> platform data. It would be a good idea at this point to split it into something
>> like this
>> 1. Introduce SOC specific c file and move the respective SOC platform data to
>> it, for ex, in this case sm8650_data
>> 2. Move the common structs from iris_platform_sm8550.c to
>> iris_platform_common.h. This way more SOCs getting added in future, can include
>> the common header to reuse them, otherwise it would end up using 8550.c for all
>> future SOC.
>>
>> Share your comments if you have any better approach to manage/re-use these
>> platform data considering more SOCs getting added.
>
> Right, yes the architecture is fine, but I don't feel iris_platform_common is
> the right
> place, perhaps we could introduce a platform_catalog.c where we could place all
> the common
> platform data and reuse them from the platform_<soc>.c files ?
Common structs would certainly need to be part of a header which can be
included. Where do you plan to keep common struct to be used across SOC specific
file in your approach ?
>
> I can design prototype on top of this patchset as an RFC.
I was thinking that the changes are not that big, and can be done in existing
series though.
Thanks,
Vikash
>
> Neil
>
>>
>> Regards,
>> Vikash
>>
>>> diff --git a/drivers/media/platform/qcom/iris/iris_probe.c
>>> b/drivers/media/platform/qcom/iris/iris_probe.c
>>> index
>>> 4f8bce6e2002bffee4c93dcaaf6e52bf4e40992e..7cd8650fbe9c09598670530103e3d5edf32953e7 100644
>>> --- a/drivers/media/platform/qcom/iris/iris_probe.c
>>> +++ b/drivers/media/platform/qcom/iris/iris_probe.c
>>> @@ -345,6 +345,10 @@ static const struct of_device_id iris_dt_match[] = {
>>> .data = &sm8250_data,
>>> },
>>> #endif
>>> + {
>>> + .compatible = "qcom,sm8650-iris",
>>> + .data = &sm8650_data,
>>> + },
>>> { },
>>> };
>>> MODULE_DEVICE_TABLE(of, iris_dt_match);
>>>
>
next prev parent reply other threads:[~2025-04-10 9:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 14:38 [PATCH v4 0/6] media: qcom: iris: add support for SM8650 Neil Armstrong
2025-04-09 14:38 ` [PATCH v4 1/6] dt-bindings: media: qcom,sm8550-iris: document SM8650 IRIS accelerator Neil Armstrong
2025-04-09 14:38 ` [PATCH v4 2/6] media: platform: qcom/iris: add power_off_controller to vpu_ops Neil Armstrong
2025-04-09 16:10 ` Vikash Garodia
2025-04-09 14:38 ` [PATCH v4 3/6] media: platform: qcom/iris: introduce optional controller_rst_tbl Neil Armstrong
2025-04-09 14:38 ` [PATCH v4 4/6] media: platform: qcom/iris: rename iris_vpu3 to iris_vpu3x Neil Armstrong
2025-04-09 16:11 ` Vikash Garodia
2025-04-10 7:19 ` Dikshita Agarwal
2025-04-09 14:38 ` [PATCH v4 5/6] media: platform: qcom/iris: add support for vpu33 Neil Armstrong
2025-04-09 14:38 ` [PATCH v4 6/6] media: platform: qcom/iris: add sm8650 support Neil Armstrong
2025-04-09 16:57 ` Vikash Garodia
2025-04-10 9:01 ` Neil Armstrong
2025-04-10 9:13 ` Vikash Garodia [this message]
2025-04-10 9:18 ` neil.armstrong
2025-04-10 13:07 ` Dikshita Agarwal
2025-04-10 15:40 ` neil.armstrong
2025-04-10 16:06 ` Bryan O'Donoghue
2025-04-10 16:30 ` neil.armstrong
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=8cade183-72ac-eac1-1a57-a9db37657fca@quicinc.com \
--to=quic_vgarodia@quicinc.com \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_dikshita@quicinc.com \
--cc=robh@kernel.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
all inboxes | Powered by JetHome®