[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46013223-5463-4164-9f61-87ea5ce2412c@kernel.org>
Date: Sat, 23 Aug 2025 17:41:21 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Mukesh Ojha <mukesh.ojha@....qualcomm.com>
Cc: Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>,
Vikash Garodia <quic_vgarodia@...cinc.com>,
Dikshita Agarwal <quic_dikshita@...cinc.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Abhinav Kumar <abhinav.kumar@...ux.dev>,
Bryan O'Donoghue <bryan.odonoghue@...aro.org>, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-media@...r.kernel.org,
linux-remoteproc@...r.kernel.org
Subject: Re: [PATCH v2 11/11] media: iris: Enable Secure PAS support with
IOMMU managed by Linux
On 22/08/2025 17:13, Mukesh Ojha wrote:
> On Fri, Aug 22, 2025 at 10:45:50AM +0200, Krzysztof Kozlowski wrote:
>> On 19/08/2025 18:54, Mukesh Ojha wrote:
>>> +int iris_fw_init(struct iris_core *core)
>>> +{
>>> + struct platform_device_info info;
>>> + struct iommu_domain *iommu_dom;
>>> + struct platform_device *pdev;
>>> + struct device_node *np;
>>> + int ret;
>>> +
>>> + np = of_get_child_by_name(core->dev->of_node, "video-firmware");
>>
>> Undocumented ABI.
>>
>> If you tested your DTS, you would notice warnings.
>
> qcom,venus-common.yaml is documenting video-firmware and getting included in
> Documentation/devicetree/bindings/media/qcom,sm8550-iris.yaml
Uh, why? Why does qcom keep this legacy pattern also for iris?
Best regards,
Krzysztof
Powered by blists - more mailing lists