Re: [PATCH v2 1/8] media: dt-bindings: qcom-kaanapali-iris: Add kaanapali video codec binding
From: Dmitry Baryshkov
Date: Wed Oct 22 2025 - 05:37:39 EST
On Wed, Oct 22, 2025 at 02:37:59AM +0530, Vikash Garodia wrote:
>
> On 10/22/2025 12:45 AM, Krzysztof Kozlowski wrote:
> > On 21/10/2025 20:55, Vikash Garodia wrote:
> >>
> >> On 10/18/2025 9:28 PM, Krzysztof Kozlowski wrote:
> >>> On 17/10/2025 16:16, Vikash Garodia wrote:
> >>>> + clock-names:
> >>>> + items:
> >>>> + - const: iface
> >>>> + - const: core
> >>>> + - const: vcodec0_core
> >>>> + - const: iface1
> >>>> + - const: core_freerun
> >>>> + - const: vcodec0_core_freerun
> >>>> + - const: vcodec_bse
> >>>> + - const: vcodec_vpp0
> >>>> + - const: vcodec_vpp1
> >>>> + - const: vcodec_apv
> >>>> +
> >>>> + dma-coherent: true
> >>>> +
> >>>> + firmware-name:
> >>>> + maxItems: 1
> >>>> +
> >>>> + interconnects:
> >>>> + maxItems: 2
> >>>> +
> >>>> + interconnect-names:
> >>>> + items:
> >>>> + - const: cpu-cfg
> >>>> + - const: video-mem
> >>>> +
> >>>> + interrupts:
> >>>> + maxItems: 1
> >>>> +
> >>>> + iommus:
> >>>> + minItems: 3
> >>>> + maxItems: 8
> >>>
> >>> I don't understand why this is flexible. Make it fixed size and anyway -
> >>> list the items.
> >>
> >> kaanapali vpu generates 8 different stream-ids. Now, boards running kernel in
> >> EL2 mode can list all of them, while boards running in EL1 can have only non
> >> secure stream IDs. Min have the list of stream ids which can be enabled for all
> >> type of boards, while max is for boards which can list all in HLOS given kernel
> >> is in EL2 mode.
> >>
> >> Below crash would be seen if boards running kernel in EL1 mode lists the secure
> >> ones.
> >
> >
> > That has to be explained somewhere, e.g. comment,
>
> Sure, will add a description for iommus property explaining the same.
>
> and still we need then
> > EL2 DTS in the kernel. I did not see such so far, but maybe I missed it
> > - can you link it?
> >
>
> EL2 DTS for kaanapali is not yet posted to handle secure SIDs. While it is in
> development, describing the secure stream-ids would ensure to cover all the
> hardware generated IDs.
EL2 is a slightly different topic, it most likely requires additional
changes, etc. I'd suggest focusing on a normal usecase first and getting
the EL2 sorted out separately.
--
With best wishes
Dmitry