[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d5c52ecf-1606-4563-ba16-a88437c414da@quicinc.com>
Date: Fri, 6 Dec 2024 22:32:32 +0800
From: Depeng Shao <quic_depengs@...cinc.com>
To: Bryan O'Donoghue <bryan.odonoghue@...aro.org>, <rfoss@...nel.org>,
<todor.too@...il.com>, <mchehab@...nel.org>, <robh@...nel.org>,
<krzk+dt@...nel.org>, <conor+dt@...nel.org>,
<vladimir.zapolskiy@...aro.org>
CC: <quic_eberman@...cinc.com>, <linux-media@...r.kernel.org>,
<linux-arm-msm@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <kernel@...cinc.com>,
Yongsheng Li
<quic_yon@...cinc.com>
Subject: Re: [PATCH 11/16] dt-bindings: media: camss: Add qcom,sm8550-camss
binding
Hi Bryan,
On 12/6/2024 6:06 PM, Bryan O'Donoghue wrote:
> On 06/12/2024 02:18, Depeng Shao wrote:
>>
>> Since the camss driver just support ife, so I think only ife related
>> iommus are needed, just like we don't add ipe,bps,jpeg related clk and
>> register in the dt-binding.
>>
>> msm_cam_smmu_ife {
>>
>> compatible = "qcom,msm-cam-smmu-cb";
>>
>> iommus = <&apps_smmu 0x800 0x20>;
>> ......
>> };
>
> Upstream camss entries provide a long list of iommu entries, please
> provide as complete a table as you can here.
>
Do you mean also add jpeg, icp and cmd's iommu entries to here? Starting
from SM8550, IFE just has one smmu entry, SM8650 and SM8750 are same.
Thanks,
Depeng
Powered by blists - more mailing lists