On 10/9/2026 3:26 PM, Krzysztof Kozlowski wrote:
> On Wed, Oct 07, 2026 at 05:07:48PM +0530, Vinayak Katoch wrote:
>> The driver uses the presence of iommu-ranges on a context bank node to
>> identify it as dedicated for extended IOVA mapping. iommu-ranges lists
>> the IOVA ranges the IOMMU allocator may use for that device; any range
>> not listed is left unused.
>>
>> Add iommu-ranges to the compute-cb subnode properties so the DT
>> validator accepts it on context bank nodes.
>
> Example looks incomplete now. Please add a new example showing complete
> picture of this device with all new properties.
>
Sure, will update.
>>
>> Relax #address-cells to enum: [1, 2] and #size-cells to enum: [0, 2] to
>> allow platforms that require 64-bit values in iommu-ranges to pass
>> binding validation.
>
> Which platforms are these?
>
Kaanapali onwards, I'll update it in the commit message.
>>
>> Signed-off-by: Vinayak Katoch <[email protected]>
>> ---
>> Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>
> Looks like this needs some dependencies.
Yes, it depends on v5 [1]. That series still has open comments, so I'll
wait until it is aligned and list it as a dependency in the next version.
[1]
https://lore.kernel.org/all/20260926-vpu_iommu_iova_handling-v5-4-0322ca5dc...@oss.qualcomm.com/
>
> Best regards,
> Krzysztof
