Kaanapali SOC brings in the new generation of video IP i.e iris4. When
compared to previous generation, iris3x, it has,
- separate power domains for stream and pixel processing hardware blocks
(bse and vpp).
- additional power domain for apv codec.
- power domains for individual pipes (VPPx).
- different clocks and reset lines.
iommu-map include all the different stream-ids which can be possibly
generated by vpu4 hardware as below,
bitstream stream from vcodec
non-pixel stream from vcodec
non-pixel stream from tensilica
pixel stream from vcodec
secure bitstream stream from vcodec
secure non-pixel stream from vcodec
secure non-pixel stream from tensilica
secure pixel stream from vcodec
firmware stream from tensilica (might be handled by the TZ / hyp)
This patch is depend on the below dt-schema patch.
Link: https://github.com/devicetree-org/dt-schema/pull/184/changes/d341298d62805bc972dfba691da6b3b62aa3ff15
Signed-off-by: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
---
.../bindings/media/qcom,kaanapali-iris.yaml | 261 +++++++++++++++++++++
include/dt-bindings/media/qcom,iris.h | 18 ++
2 files changed, 279 insertions(+)
diff --git a/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.yaml b/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.yaml
new file mode 100644
index 0000000000000000000000000000000000000000..db734c664a0417d8f5ea55b066f63f42583b1c14
--- /dev/null
+++ b/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.yaml
@@ -0,0 +1,261 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/media/qcom,kaanapali-iris.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Qualcomm Kaanapali Iris video encoder and decoder
+
+maintainers:
+ - Vikash Garodia <vikash.garodia@oss.qualcomm.com>
+ - Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>
+
+description:
+ The iris video processing unit is a video encode and decode accelerator
+ present on Qualcomm Kaanapali SoC.
+
+definitions:
+ iommu-types:
+ items:
+ - description: Function ID
+ - description: Phandle to IOMMU
+ - description: IOMMU stream ID base
+ - description: IOMMU stream ID mask
+ - description: Number of stream IDs
+
+properties:
+ compatible:
+ const: qcom,kaanapali-iris
+
+ reg:
+ maxItems: 1
+
+ clocks:
+ maxItems: 10
+
+ 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
+
+ iommu-map:
+ description: |
+ - bitstream stream from vcodec
+ - non-pixel stream from vcodec
+ - non-pixel stream from tensilica
+ - pixel stream from vcodec
+ - secure bitstream stream from vcodec
+ - secure non-pixel stream from vcodec
+ - secure non-pixel stream from tensilica
+ - secure pixel stream from vcodec
+ # firmware might be handled by the TZ / hyp
+ - firmware stream from tensilica
+ $ref: /schemas/types.yaml#/definitions/uint32-matrix
+ items:
+ $ref: '#/definitions/iommu-types'
+ minItems: 5
+ minItems: 8
+ maxItems: 9
+
+ memory-region:
+ maxItems: 1
+
+ operating-points-v2: true
+ opp-table:
+ type: object
+
+ power-domains:
+ maxItems: 7
+
+ power-domain-names:
+ items:
+ - const: venus
+ - const: vcodec0
+ - const: mxc
+ - const: mmcx
+ - const: vpp0
+ - const: vpp1
+ - const: apv
+
+ resets:
+ maxItems: 4
+
+ reset-names:
+ items:
+ - const: bus0
+ - const: bus1
+ - const: core
+ - const: vcodec0_core
+
+required:
+ - compatible
+ - reg
+ - clocks
+ - clock-names
+ - dma-coherent
+ - interconnects
+ - interconnect-names
+ - interrupts
+ - iommu-map
+ - memory-region
+ - power-domains
+ - power-domain-names
+ - resets
+ - reset-names
+
+unevaluatedProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/interrupt-controller/arm-gic.h>
+ #include <dt-bindings/media/qcom,iris.h>
+ #include <dt-bindings/power/qcom,rpmhpd.h>
+
+ video-codec@2000000 {
+ compatible = "qcom,kaanapali-iris";
+ reg = <0x02000000 0xf0000>;
+
+ clocks = <&gcc_video_axi0_clk>,
+ <&video_cc_mvs0c_clk>,
+ <&video_cc_mvs0_clk>,
+ <&gcc_video_axi1_clk>,
+ <&video_cc_mvs0c_freerun_clk>,
+ <&video_cc_mvs0_freerun_clk>,
+ <&video_cc_mvs0b_clk>,
+ <&video_cc_mvs0_vpp0_clk>,
+ <&video_cc_mvs0_vpp1_clk>,
+ <&video_cc_mvs0a_clk>;
+ clock-names = "iface",
+ "core",
+ "vcodec0_core",
+ "iface1",
+ "core_freerun",
+ "vcodec0_core_freerun",
+ "vcodec_bse",
+ "vcodec_vpp0",
+ "vcodec_vpp1",
+ "vcodec_apv";
+
+ dma-coherent;
+
+ interconnects = <&gem_noc_master_appss_proc &config_noc_slave_venus_cfg>,
+ <&mmss_noc_master_video_mvp &mc_virt_slave_ebi1>;
+ interconnect-names = "cpu-cfg",
+ "video-mem";
+
+ interrupts = <GIC_SPI 174 IRQ_TYPE_LEVEL_HIGH>;
+
+ iommu-map = <IRIS_BITSTREAM &apps_smmu 0x1944 0x0 0x1>,
+ <IRIS_NON_PIXEL &apps_smmu 0x1940 0x0 0x1>,
+ <IRIS_NON_PIXEL &apps_smmu 0x1a20 0x0 0x1>,
+ <IRIS_PIXEL &apps_smmu 0x1943 0x0 0x1>,
+ <IRIS_SECURE_BITSTREAM &apps_smmu 0x1946 0x0 0x1>,
+ <IRIS_SECURE_NON_PIXEL &apps_smmu 0x1941 0x0 0x1>,
+ <IRIS_SECURE_NON_PIXEL &apps_smmu 0x1a21 0x0 0x1>,
+ <IRIS_SECURE_PIXEL &apps_smmu 0x1945 0x0 0x1>,
+ <IRIS_FIRMWARE &apps_smmu 0x1a22 0x0 0x1>;
+
+ memory-region = <&video_mem>;
+
+ operating-points-v2 = <&iris_opp_table>;
+
+ power-domains = <&video_cc_mvs0c_gdsc>,
+ <&video_cc_mvs0_gdsc>,
+ <&rpmhpd RPMHPD_MXC>,
+ <&rpmhpd RPMHPD_MMCX>,
+ <&video_cc_mvs0_vpp0_gdsc>,
+ <&video_cc_mvs0_vpp1_gdsc>,
+ <&video_cc_mvs0a_gdsc>;
+ power-domain-names = "venus",
+ "vcodec0",
+ "mxc",
+ "mmcx",
+ "vpp0",
+ "vpp1",
+ "apv";
+
+ resets = <&gcc_video_axi0_clk_ares>,
+ <&gcc_video_axi1_clk_ares>,
+ <&video_cc_mvs0c_freerun_clk_ares>,
+ <&video_cc_mvs0_freerun_clk_ares>;
+ reset-names = "bus0",
+ "bus1",
+ "core",
+ "vcodec0_core";
+
+ iris_opp_table: opp-table {
+ compatible = "operating-points-v2";
+
+ opp-240000000 {
+ opp-hz = /bits/ 64 <240000000 240000000 240000000 360000000>;
+ required-opps = <&rpmhpd_opp_low_svs_d1>,
+ <&rpmhpd_opp_low_svs_d1>;
+ };
+
+ opp-338000000 {
+ opp-hz = /bits/ 64 <338000000 338000000 338000000 507000000>;
+ required-opps = <&rpmhpd_opp_low_svs>,
+ <&rpmhpd_opp_low_svs>;
+ };
+
+ opp-420000000 {
+ opp-hz = /bits/ 64 <420000000 420000000 420000000 630000000>;
+ required-opps = <&rpmhpd_opp_svs>,
+ <&rpmhpd_opp_svs>;
+ };
+
+ opp-444000000 {
+ opp-hz = /bits/ 64 <444000000 444000000 444000000 666000000>;
+ required-opps = <&rpmhpd_opp_svs_l1>,
+ <&rpmhpd_opp_svs_l1>;
+ };
+
+ opp-533000000 {
+ opp-hz = /bits/ 64 <533000000 533000000 533000000 800000000>;
+ required-opps = <&rpmhpd_opp_nom>,
+ <&rpmhpd_opp_nom>;
+ };
+
+ opp-630000000 {
+ opp-hz = /bits/ 64 <630000000 630000000 630000000 1104000000>;
+ required-opps = <&rpmhpd_opp_turbo>,
+ <&rpmhpd_opp_turbo>;
+ };
+
+ opp-800000000 {
+ opp-hz = /bits/ 64 <800000000 630000000 630000000 1260000000>;
+ required-opps = <&rpmhpd_opp_turbo_l0>,
+ <&rpmhpd_opp_turbo_l0>;
+ };
+
+ opp-1000000000 {
+ opp-hz = /bits/ 64 <1000000000 630000000 850000000 1260000000>;
+ required-opps = <&rpmhpd_opp_turbo_l1>,
+ <&rpmhpd_opp_turbo_l1>;
+ };
+ };
+ };
diff --git a/include/dt-bindings/media/qcom,iris.h b/include/dt-bindings/media/qcom,iris.h
new file mode 100644
index 0000000000000000000000000000000000000000..beb244289466ca938c7e5fe5cf15526f606a3a6c
--- /dev/null
+++ b/include/dt-bindings/media/qcom,iris.h
@@ -0,0 +1,18 @@
+/* SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) */
+/*
+ * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
+ */
+
+#ifndef _DT_BINDINGS_MEDIA_QCOM_IRIS_H
+#define _DT_BINDINGS_MEDIA_QCOM_IRIS_H
+
+/* Function identifiers for iommu-map to attach for the context bank devices */
+#define IRIS_BITSTREAM 0x100
+#define IRIS_NON_PIXEL 0x101
+#define IRIS_PIXEL 0x102
+#define IRIS_SECURE_BITSTREAM 0x200
+#define IRIS_SECURE_NON_PIXEL 0x201
+#define IRIS_SECURE_PIXEL 0x202
+#define IRIS_FIRMWARE 0x300
+
+#endif
--
2.34.1On Fri, Feb 27, 2026 at 07:41:17PM +0530, Vikash Garodia wrote: > Kaanapali SOC brings in the new generation of video IP i.e iris4. When > compared to previous generation, iris3x, it has, > - separate power domains for stream and pixel processing hardware blocks > (bse and vpp). > - additional power domain for apv codec. > - power domains for individual pipes (VPPx). > - different clocks and reset lines. > > iommu-map include all the different stream-ids which can be possibly > generated by vpu4 hardware as below, > bitstream stream from vcodec > non-pixel stream from vcodec > non-pixel stream from tensilica > pixel stream from vcodec > secure bitstream stream from vcodec > secure non-pixel stream from vcodec > secure non-pixel stream from tensilica > secure pixel stream from vcodec > firmware stream from tensilica (might be handled by the TZ / hyp) > > This patch is depend on the below dt-schema patch. > Link: https://github.com/devicetree-org/dt-schema/pull/184/changes/d341298d62805bc972dfba691da6b3b62aa3ff15 > Signed-off-by: Vikash Garodia <vikash.garodia@oss.qualcomm.com> > --- > .../bindings/media/qcom,kaanapali-iris.yaml | 261 +++++++++++++++++++++ > include/dt-bindings/media/qcom,iris.h | 18 ++ > 2 files changed, 279 insertions(+) > > + > + iommu-map: > + description: | > + - bitstream stream from vcodec > + - non-pixel stream from vcodec > + - non-pixel stream from tensilica > + - pixel stream from vcodec > + - secure bitstream stream from vcodec > + - secure non-pixel stream from vcodec > + - secure non-pixel stream from tensilica > + - secure pixel stream from vcodec > + # firmware might be handled by the TZ / hyp > + - firmware stream from tensilica Why are you providing description as a list rather than describing each item separately? Then you wouldn't need maxItems. > + $ref: /schemas/types.yaml#/definitions/uint32-matrix > + items: > + $ref: '#/definitions/iommu-types' > + minItems: 5 > + minItems: 8 > + maxItems: 9 > + -- With best wishes Dmitry
On 2/28/2026 1:22 AM, Dmitry Baryshkov wrote:
> On Fri, Feb 27, 2026 at 07:41:17PM +0530, Vikash Garodia wrote:
>> Kaanapali SOC brings in the new generation of video IP i.e iris4. When
>> compared to previous generation, iris3x, it has,
>> - separate power domains for stream and pixel processing hardware blocks
>> (bse and vpp).
>> - additional power domain for apv codec.
>> - power domains for individual pipes (VPPx).
>> - different clocks and reset lines.
>>
>> iommu-map include all the different stream-ids which can be possibly
>> generated by vpu4 hardware as below,
>> bitstream stream from vcodec
>> non-pixel stream from vcodec
>> non-pixel stream from tensilica
>> pixel stream from vcodec
>> secure bitstream stream from vcodec
>> secure non-pixel stream from vcodec
>> secure non-pixel stream from tensilica
>> secure pixel stream from vcodec
>> firmware stream from tensilica (might be handled by the TZ / hyp)
>>
>> This patch is depend on the below dt-schema patch.
>> Link: https://github.com/devicetree-org/dt-schema/pull/184/changes/d341298d62805bc972dfba691da6b3b62aa3ff15
>> Signed-off-by: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
>> ---
>> .../bindings/media/qcom,kaanapali-iris.yaml | 261 +++++++++++++++++++++
>> include/dt-bindings/media/qcom,iris.h | 18 ++
>> 2 files changed, 279 insertions(+)
>>
>> +
>> + iommu-map:
>> + description: |
>> + - bitstream stream from vcodec
>> + - non-pixel stream from vcodec
>> + - non-pixel stream from tensilica
>> + - pixel stream from vcodec
>> + - secure bitstream stream from vcodec
>> + - secure non-pixel stream from vcodec
>> + - secure non-pixel stream from tensilica
>> + - secure pixel stream from vcodec
>> + # firmware might be handled by the TZ / hyp
>> + - firmware stream from tensilica
>
> Why are you providing description as a list rather than describing each
> item separately? Then you wouldn't need maxItems.
>
rewrote them as below and dropped maxItems. Please review.
iommu-map:
$ref: /schemas/types.yaml#/definitions/uint32-matrix
items:
- description: bitstream stream from vcodec
items:
- description: Function ID
- description: Phandle to IOMMU
- description: IOMMU stream ID base
- description: IOMMU stream ID mask
- description: Number of stream IDs
- description: non-pixel stream from vcodec
- description: non-pixel stream from tensilica
- description: pixel stream from vcodec
- description: secure bitstream stream from vcodec
- description: secure non-pixel stream from vcodec
- description: secure non-pixel stream from tensilica
- description: secure pixel stream from vcodec
# firmware might be handled by the TZ / hyp
- description: firmware stream from tensilica
minItems: 8
>> + $ref: /schemas/types.yaml#/definitions/uint32-matrix
>> + items:
>> + $ref: '#/definitions/iommu-types'
>> + minItems: 5
>> + minItems: 8
>> + maxItems: 9
>> +
>
Regards,
Vikash
On Tue, Mar 03, 2026 at 11:43:40PM +0530, Vikash Garodia wrote: > > > On 2/28/2026 1:22 AM, Dmitry Baryshkov wrote: > > On Fri, Feb 27, 2026 at 07:41:17PM +0530, Vikash Garodia wrote: > > > Kaanapali SOC brings in the new generation of video IP i.e iris4. When > > > compared to previous generation, iris3x, it has, > > > - separate power domains for stream and pixel processing hardware blocks > > > (bse and vpp). > > > - additional power domain for apv codec. > > > - power domains for individual pipes (VPPx). > > > - different clocks and reset lines. > > > > > > iommu-map include all the different stream-ids which can be possibly > > > generated by vpu4 hardware as below, > > > bitstream stream from vcodec > > > non-pixel stream from vcodec > > > non-pixel stream from tensilica > > > pixel stream from vcodec > > > secure bitstream stream from vcodec > > > secure non-pixel stream from vcodec > > > secure non-pixel stream from tensilica > > > secure pixel stream from vcodec > > > firmware stream from tensilica (might be handled by the TZ / hyp) > > > > > > This patch is depend on the below dt-schema patch. > > > Link: https://github.com/devicetree-org/dt-schema/pull/184/changes/d341298d62805bc972dfba691da6b3b62aa3ff15 > > > Signed-off-by: Vikash Garodia <vikash.garodia@oss.qualcomm.com> > > > --- > > > .../bindings/media/qcom,kaanapali-iris.yaml | 261 +++++++++++++++++++++ > > > include/dt-bindings/media/qcom,iris.h | 18 ++ > > > 2 files changed, 279 insertions(+) > > > > > > + > > > + iommu-map: > > > + description: | > > > + - bitstream stream from vcodec > > > + - non-pixel stream from vcodec > > > + - non-pixel stream from tensilica > > > + - pixel stream from vcodec > > > + - secure bitstream stream from vcodec > > > + - secure non-pixel stream from vcodec > > > + - secure non-pixel stream from tensilica > > > + - secure pixel stream from vcodec > > > + # firmware might be handled by the TZ / hyp > > > + - firmware stream from tensilica > > > > Why are you providing description as a list rather than describing each > > item separately? Then you wouldn't need maxItems. > > > > rewrote them as below and dropped maxItems. Please review. > > iommu-map: > $ref: /schemas/types.yaml#/definitions/uint32-matrix > items: > - description: bitstream stream from vcodec > items: > - description: Function ID > - description: Phandle to IOMMU > - description: IOMMU stream ID base > - description: IOMMU stream ID mask > - description: Number of stream IDs I'm not a pro in the DT. Is the itemization of the first item reused for the rest of the items? > - description: non-pixel stream from vcodec > - description: non-pixel stream from tensilica > - description: pixel stream from vcodec > - description: secure bitstream stream from vcodec > - description: secure non-pixel stream from vcodec > - description: secure non-pixel stream from tensilica > - description: secure pixel stream from vcodec > # firmware might be handled by the TZ / hyp > - description: firmware stream from tensilica > minItems: 8 > > > > + $ref: /schemas/types.yaml#/definitions/uint32-matrix > > > + items: > > > + $ref: '#/definitions/iommu-types' > > > + minItems: 5 > > > + minItems: 8 > > > + maxItems: 9 > > > + > > > > Regards, > Vikash -- With best wishes Dmitry
On 3/4/2026 5:23 AM, Dmitry Baryshkov wrote: > On Tue, Mar 03, 2026 at 11:43:40PM +0530, Vikash Garodia wrote: >> >> >> On 2/28/2026 1:22 AM, Dmitry Baryshkov wrote: >>> On Fri, Feb 27, 2026 at 07:41:17PM +0530, Vikash Garodia wrote: >>>> Kaanapali SOC brings in the new generation of video IP i.e iris4. When >>>> compared to previous generation, iris3x, it has, >>>> - separate power domains for stream and pixel processing hardware blocks >>>> (bse and vpp). >>>> - additional power domain for apv codec. >>>> - power domains for individual pipes (VPPx). >>>> - different clocks and reset lines. >>>> >>>> iommu-map include all the different stream-ids which can be possibly >>>> generated by vpu4 hardware as below, >>>> bitstream stream from vcodec >>>> non-pixel stream from vcodec >>>> non-pixel stream from tensilica >>>> pixel stream from vcodec >>>> secure bitstream stream from vcodec >>>> secure non-pixel stream from vcodec >>>> secure non-pixel stream from tensilica >>>> secure pixel stream from vcodec >>>> firmware stream from tensilica (might be handled by the TZ / hyp) >>>> >>>> This patch is depend on the below dt-schema patch. >>>> Link: https://github.com/devicetree-org/dt-schema/pull/184/changes/d341298d62805bc972dfba691da6b3b62aa3ff15 >>>> Signed-off-by: Vikash Garodia <vikash.garodia@oss.qualcomm.com> >>>> --- >>>> .../bindings/media/qcom,kaanapali-iris.yaml | 261 +++++++++++++++++++++ >>>> include/dt-bindings/media/qcom,iris.h | 18 ++ >>>> 2 files changed, 279 insertions(+) >>>> >>>> + >>>> + iommu-map: >>>> + description: | >>>> + - bitstream stream from vcodec >>>> + - non-pixel stream from vcodec >>>> + - non-pixel stream from tensilica >>>> + - pixel stream from vcodec >>>> + - secure bitstream stream from vcodec >>>> + - secure non-pixel stream from vcodec >>>> + - secure non-pixel stream from tensilica >>>> + - secure pixel stream from vcodec >>>> + # firmware might be handled by the TZ / hyp >>>> + - firmware stream from tensilica >>> >>> Why are you providing description as a list rather than describing each >>> item separately? Then you wouldn't need maxItems. >>> >> >> rewrote them as below and dropped maxItems. Please review. >> >> iommu-map: >> $ref: /schemas/types.yaml#/definitions/uint32-matrix >> items: >> - description: bitstream stream from vcodec >> items: >> - description: Function ID >> - description: Phandle to IOMMU >> - description: IOMMU stream ID base >> - description: IOMMU stream ID mask >> - description: Number of stream IDs > > I'm not a pro in the DT. Is the itemization of the first item reused for > the rest of the items? yes. As a trial, if i remove one of the itemization from above schema, then checker throws error saying 5x9 arguments in the example is *too long* as it tries to fit it as per schema i.e 4x9. > >> - description: non-pixel stream from vcodec >> - description: non-pixel stream from tensilica >> - description: pixel stream from vcodec >> - description: secure bitstream stream from vcodec >> - description: secure non-pixel stream from vcodec >> - description: secure non-pixel stream from tensilica >> - description: secure pixel stream from vcodec >> # firmware might be handled by the TZ / hyp >> - description: firmware stream from tensilica >> minItems: 8 >> >>>> + $ref: /schemas/types.yaml#/definitions/uint32-matrix >>>> + items: >>>> + $ref: '#/definitions/iommu-types' >>>> + minItems: 5 >>>> + minItems: 8 >>>> + maxItems: 9 >>>> + >>> >> >> Regards, >> Vikash >
On Wed, Mar 04, 2026 at 08:32:53PM +0530, Vikash Garodia wrote: > > > On 3/4/2026 5:23 AM, Dmitry Baryshkov wrote: > > On Tue, Mar 03, 2026 at 11:43:40PM +0530, Vikash Garodia wrote: > > > > > > > > > On 2/28/2026 1:22 AM, Dmitry Baryshkov wrote: > > > > On Fri, Feb 27, 2026 at 07:41:17PM +0530, Vikash Garodia wrote: > > > > > Kaanapali SOC brings in the new generation of video IP i.e iris4. When > > > > > compared to previous generation, iris3x, it has, > > > > > - separate power domains for stream and pixel processing hardware blocks > > > > > (bse and vpp). > > > > > - additional power domain for apv codec. > > > > > - power domains for individual pipes (VPPx). > > > > > - different clocks and reset lines. > > > > > > > > > > iommu-map include all the different stream-ids which can be possibly > > > > > generated by vpu4 hardware as below, > > > > > bitstream stream from vcodec > > > > > non-pixel stream from vcodec > > > > > non-pixel stream from tensilica > > > > > pixel stream from vcodec > > > > > secure bitstream stream from vcodec > > > > > secure non-pixel stream from vcodec > > > > > secure non-pixel stream from tensilica > > > > > secure pixel stream from vcodec > > > > > firmware stream from tensilica (might be handled by the TZ / hyp) > > > > > > > > > > This patch is depend on the below dt-schema patch. > > > > > Link: https://github.com/devicetree-org/dt-schema/pull/184/changes/d341298d62805bc972dfba691da6b3b62aa3ff15 > > > > > Signed-off-by: Vikash Garodia <vikash.garodia@oss.qualcomm.com> > > > > > --- > > > > > .../bindings/media/qcom,kaanapali-iris.yaml | 261 +++++++++++++++++++++ > > > > > include/dt-bindings/media/qcom,iris.h | 18 ++ > > > > > 2 files changed, 279 insertions(+) > > > > > > > > > > + > > > > > + iommu-map: > > > > > + description: | > > > > > + - bitstream stream from vcodec > > > > > + - non-pixel stream from vcodec > > > > > + - non-pixel stream from tensilica > > > > > + - pixel stream from vcodec > > > > > + - secure bitstream stream from vcodec > > > > > + - secure non-pixel stream from vcodec > > > > > + - secure non-pixel stream from tensilica > > > > > + - secure pixel stream from vcodec > > > > > + # firmware might be handled by the TZ / hyp > > > > > + - firmware stream from tensilica > > > > > > > > Why are you providing description as a list rather than describing each > > > > item separately? Then you wouldn't need maxItems. > > > > > > > > > > rewrote them as below and dropped maxItems. Please review. > > > > > > iommu-map: > > > $ref: /schemas/types.yaml#/definitions/uint32-matrix > > > items: > > > - description: bitstream stream from vcodec > > > items: > > > - description: Function ID > > > - description: Phandle to IOMMU > > > - description: IOMMU stream ID base > > > - description: IOMMU stream ID mask > > > - description: Number of stream IDs > > > > I'm not a pro in the DT. Is the itemization of the first item reused for > > the rest of the items? > > yes. As a trial, if i remove one of the itemization from above schema, then > checker throws error saying 5x9 arguments in the example is *too long* as it > tries to fit it as per schema i.e 4x9. Ack, thanks for the test! > > > > > > - description: non-pixel stream from vcodec > > > - description: non-pixel stream from tensilica > > > - description: pixel stream from vcodec > > > - description: secure bitstream stream from vcodec > > > - description: secure non-pixel stream from vcodec > > > - description: secure non-pixel stream from tensilica > > > - description: secure pixel stream from vcodec > > > # firmware might be handled by the TZ / hyp > > > - description: firmware stream from tensilica > > > minItems: 8 > > > > > > > > + $ref: /schemas/types.yaml#/definitions/uint32-matrix > > > > > + items: > > > > > + $ref: '#/definitions/iommu-types' > > > > > + minItems: 5 > > > > > + minItems: 8 > > > > > + maxItems: 9 > > > > > + > > > > > > > > > > Regards, > > > Vikash > > > -- With best wishes Dmitry
On 27/02/2026 15:11, Vikash Garodia wrote: > Kaanapali SOC brings in the new generation of video IP i.e iris4. When > compared to previous generation, iris3x, it has, > - separate power domains for stream and pixel processing hardware blocks > (bse and vpp). > - additional power domain for apv codec. > - power domains for individual pipes (VPPx). > - different clocks and reset lines. > > iommu-map include all the different stream-ids which can be possibly > generated by vpu4 hardware as below, > bitstream stream from vcodec > non-pixel stream from vcodec > non-pixel stream from tensilica > pixel stream from vcodec > secure bitstream stream from vcodec > secure non-pixel stream from vcodec > secure non-pixel stream from tensilica > secure pixel stream from vcodec > firmware stream from tensilica (might be handled by the TZ / hyp) I cannot really parse above. > > This patch is depend on the below dt-schema patch. > Link: https://github.com/devicetree-org/dt-schema/pull/184/changes/d341298d62805bc972dfba691da6b3b62aa3ff15 > Signed-off-by: Vikash Garodia <vikash.garodia@oss.qualcomm.com> > --- > .../bindings/media/qcom,kaanapali-iris.yaml | 261 +++++++++++++++++++++ > include/dt-bindings/media/qcom,iris.h | 18 ++ > 2 files changed, 279 insertions(+) > > diff --git a/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.yaml b/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.yaml > new file mode 100644 > index 0000000000000000000000000000000000000000..db734c664a0417d8f5ea55b066f63f42583b1c14 > --- /dev/null > +++ b/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.yaml > @@ -0,0 +1,261 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/media/qcom,kaanapali-iris.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Qualcomm Kaanapali Iris video encoder and decoder > + > +maintainers: > + - Vikash Garodia <vikash.garodia@oss.qualcomm.com> > + - Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com> > + > +description: > + The iris video processing unit is a video encode and decode accelerator > + present on Qualcomm Kaanapali SoC. > + > +definitions: > + iommu-types: > + items: > + - description: Function ID > + - description: Phandle to IOMMU > + - description: IOMMU stream ID base > + - description: IOMMU stream ID mask > + - description: Number of stream IDs You don't need definitions. > + > +properties: > + compatible: > + const: qcom,kaanapali-iris > + > + reg: > + maxItems: 1 > + > + clocks: > + maxItems: 10 > + > + 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 > + > + iommu-map: > + description: | > + - bitstream stream from vcodec > + - non-pixel stream from vcodec > + - non-pixel stream from tensilica > + - pixel stream from vcodec > + - secure bitstream stream from vcodec > + - secure non-pixel stream from vcodec > + - secure non-pixel stream from tensilica > + - secure pixel stream from vcodec > + # firmware might be handled by the TZ / hyp > + - firmware stream from tensilica Drop description, pointless. How does it help anyhow in writing DTS? > + $ref: /schemas/types.yaml#/definitions/uint32-matrix > + items: > + $ref: '#/definitions/iommu-types' > + minItems: 5 > + minItems: 8 > + maxItems: 9 This solves nothing from the discussions we had. I re-iterated multiple times, plus there were internal threads doing the same, that you need to define the items to have strict order. > + > + memory-region: > + maxItems: 1 > + > + operating-points-v2: true > + opp-table: > + type: object > + > + power-domains: > + maxItems: 7 > + > + power-domain-names: > + items: > + - const: venus > + - const: vcodec0 > + - const: mxc > + - const: mmcx > + - const: vpp0 > + - const: vpp1 > + - const: apv > + > + resets: > + maxItems: 4 > + > + reset-names: > + items: > + - const: bus0 > + - const: bus1 > + - const: core > + - const: vcodec0_core > + I assume you checked and used last SoC order of all the entries here. > +required: > + - compatible > + - reg > + - clocks > + - clock-names > + - dma-coherent > + - interconnects > + - interconnect-names > + - interrupts > + - iommu-map > + - memory-region > + - power-domains > + - power-domain-names > + - resets > + - reset-names > + > +unevaluatedProperties: false additionalprops, see writing schema for explanation. ... > + }; > diff --git a/include/dt-bindings/media/qcom,iris.h b/include/dt-bindings/media/qcom,iris.h Filename must match binding/compatible. I asked for this multiple times. > new file mode 100644 > index 0000000000000000000000000000000000000000..beb244289466ca938c7e5fe5cf15526f606a3a6c > --- /dev/null > +++ b/include/dt-bindings/media/qcom,iris.h > @@ -0,0 +1,18 @@ > +/* SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) */ > +/* > + * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries. > + */ > + > +#ifndef _DT_BINDINGS_MEDIA_QCOM_IRIS_H > +#define _DT_BINDINGS_MEDIA_QCOM_IRIS_H > + > +/* Function identifiers for iommu-map to attach for the context bank devices */ > +#define IRIS_BITSTREAM 0x100 > +#define IRIS_NON_PIXEL 0x101 > +#define IRIS_PIXEL 0x102 > +#define IRIS_SECURE_BITSTREAM 0x200 > +#define IRIS_SECURE_NON_PIXEL 0x201 > +#define IRIS_SECURE_PIXEL 0x202 > +#define IRIS_FIRMWARE 0x300 > + Abstract identifiers for ABI start with 0 or 1 and are incremented by 1, not 0x100. There are also decimal, not hex. Best regards, Krzysztof
On 2/27/2026 9:20 PM, Krzysztof Kozlowski wrote:
> On 27/02/2026 15:11, Vikash Garodia wrote:
>> Kaanapali SOC brings in the new generation of video IP i.e iris4. When
>> compared to previous generation, iris3x, it has,
>> - separate power domains for stream and pixel processing hardware blocks
>> (bse and vpp).
>> - additional power domain for apv codec.
>> - power domains for individual pipes (VPPx).
>> - different clocks and reset lines.
>>
>> iommu-map include all the different stream-ids which can be possibly
>> generated by vpu4 hardware as below,
>> bitstream stream from vcodec
>> non-pixel stream from vcodec
>> non-pixel stream from tensilica
>> pixel stream from vcodec
>> secure bitstream stream from vcodec
>> secure non-pixel stream from vcodec
>> secure non-pixel stream from tensilica
>> secure pixel stream from vcodec
>> firmware stream from tensilica (might be handled by the TZ / hyp)
>
> I cannot really parse above.
I think its better to drop this aspect from commit message, as the patch
precisely describes them.
>
>>
>> This patch is depend on the below dt-schema patch.
>> Link: https://github.com/devicetree-org/dt-schema/pull/184/changes/d341298d62805bc972dfba691da6b3b62aa3ff15
>> Signed-off-by: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
>> ---
>> .../bindings/media/qcom,kaanapali-iris.yaml | 261 +++++++++++++++++++++
>> include/dt-bindings/media/qcom,iris.h | 18 ++
>> 2 files changed, 279 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.yaml b/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.yaml
>> new file mode 100644
>> index 0000000000000000000000000000000000000000..db734c664a0417d8f5ea55b066f63f42583b1c14
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.yaml
>> @@ -0,0 +1,261 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/media/qcom,kaanapali-iris.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Qualcomm Kaanapali Iris video encoder and decoder
>> +
>> +maintainers:
>> + - Vikash Garodia <vikash.garodia@oss.qualcomm.com>
>> + - Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>
>> +
>> +description:
>> + The iris video processing unit is a video encode and decode accelerator
>> + present on Qualcomm Kaanapali SoC.
>> +
>> +definitions:
>> + iommu-types:
>> + items:
>> + - description: Function ID
>> + - description: Phandle to IOMMU
>> + - description: IOMMU stream ID base
>> + - description: IOMMU stream ID mask
>> + - description: Number of stream IDs
>
> You don't need definitions.
Ack, this can be dropped altogether.
>
>> +
>> +properties:
>> + compatible:
>> + const: qcom,kaanapali-iris
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + clocks:
>> + maxItems: 10
>> +
>> + 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
>> +
>> + iommu-map:
>> + description: |
>> + - bitstream stream from vcodec
>> + - non-pixel stream from vcodec
>> + - non-pixel stream from tensilica
>> + - pixel stream from vcodec
>> + - secure bitstream stream from vcodec
>> + - secure non-pixel stream from vcodec
>> + - secure non-pixel stream from tensilica
>> + - secure pixel stream from vcodec
>> + # firmware might be handled by the TZ / hyp
>> + - firmware stream from tensilica
>
> Drop description, pointless. How does it help anyhow in writing DTS?
>
>> + $ref: /schemas/types.yaml#/definitions/uint32-matrix
>> + items:
>> + $ref: '#/definitions/iommu-types'
>> + minItems: 5
>> + minItems: 8
>> + maxItems: 9
>
> This solves nothing from the discussions we had. I re-iterated multiple
> times, plus there were internal threads doing the same, that you need to
> define the items to have strict order.
>
describing them as a list of items, please review.
iommu-map:
$ref: /schemas/types.yaml#/definitions/uint32-matrix
items:
- description: bitstream stream from vcodec
items:
- description: Function ID
- description: Phandle to IOMMU
- description: IOMMU stream ID base
- description: IOMMU stream ID mask
- description: Number of stream IDs
- description: non-pixel stream from vcodec
- description: non-pixel stream from tensilica
- description: pixel stream from vcodec
- description: secure bitstream stream from vcodec
- description: secure non-pixel stream from vcodec
- description: secure non-pixel stream from tensilica
- description: secure pixel stream from vcodec
# firmware might be handled by the TZ / hyp
- description: firmware stream from tensilica
minItems: 8
>> +
>> + memory-region:
>> + maxItems: 1
>> +
>> + operating-points-v2: true
>> + opp-table:
>> + type: object
>> +
>> + power-domains:
>> + maxItems: 7
>> +
>> + power-domain-names:
>> + items:
>> + - const: venus
>> + - const: vcodec0
>> + - const: mxc
>> + - const: mmcx
>> + - const: vpp0
>> + - const: vpp1
>> + - const: apv
>> +
>> + resets:
>> + maxItems: 4
>> +
>> + reset-names:
>> + items:
>> + - const: bus0
>> + - const: bus1
>> + - const: core
>> + - const: vcodec0_core
>> +
>
> I assume you checked and used last SoC order of all the entries here.
yes, order is followed as used in earlier SOC.
>
>
>> +required:
>> + - compatible
>> + - reg
>> + - clocks
>> + - clock-names
>> + - dma-coherent
>> + - interconnects
>> + - interconnect-names
>> + - interrupts
>> + - iommu-map
>> + - memory-region
>> + - power-domains
>> + - power-domain-names
>> + - resets
>> + - reset-names
>> +
>> +unevaluatedProperties: false
>
> additionalprops, see writing schema for explanation.
>
I do not see this being added in qcom,sm8750-iris.yaml as well. Since
you made that schema, i generally follow that as reference.
>
> ...
>
>> + };
>> diff --git a/include/dt-bindings/media/qcom,iris.h b/include/dt-bindings/media/qcom,iris.h
>
> Filename must match binding/compatible. I asked for this multiple times.
>
in this case, its applicable for other platforms as well. Naming it as
qcom,kaanapali-iris.h would make it look like kaanapali specific.
>> new file mode 100644
>> index 0000000000000000000000000000000000000000..beb244289466ca938c7e5fe5cf15526f606a3a6c
>> --- /dev/null
>> +++ b/include/dt-bindings/media/qcom,iris.h
>> @@ -0,0 +1,18 @@
>> +/* SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) */
>> +/*
>> + * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
>> + */
>> +
>> +#ifndef _DT_BINDINGS_MEDIA_QCOM_IRIS_H
>> +#define _DT_BINDINGS_MEDIA_QCOM_IRIS_H
>> +
>> +/* Function identifiers for iommu-map to attach for the context bank devices */
>> +#define IRIS_BITSTREAM 0x100
>> +#define IRIS_NON_PIXEL 0x101
>> +#define IRIS_PIXEL 0x102
>> +#define IRIS_SECURE_BITSTREAM 0x200
>> +#define IRIS_SECURE_NON_PIXEL 0x201
>> +#define IRIS_SECURE_PIXEL 0x202
>> +#define IRIS_FIRMWARE 0x300
>> +
>
> Abstract identifiers for ABI start with 0 or 1 and are incremented by 1,
> not 0x100. There are also decimal, not hex.
Ack.
>
> Best regards,
> Krzysztof
Regards,
Vikash
On 03/03/2026 19:10, Vikash Garodia wrote: > >> >> ... >> >>> + }; >>> diff --git a/include/dt-bindings/media/qcom,iris.h b/include/dt-bindings/media/qcom,iris.h >> >> Filename must match binding/compatible. I asked for this multiple times. >> > > in this case, its applicable for other platforms as well. Naming it as > qcom,kaanapali-iris.h would make it look like kaanapali specific. I repeated that feedback way too many times. NAK Nacked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com Best regards, Krzysztof
On 3/4/2026 8:37 PM, Krzysztof Kozlowski wrote: > On 03/03/2026 19:10, Vikash Garodia wrote: >> >>> >>> ... >>> >>>> + }; >>>> diff --git a/include/dt-bindings/media/qcom,iris.h b/include/dt-bindings/media/qcom,iris.h >>> >>> Filename must match binding/compatible. I asked for this multiple times. >>> >> >> in this case, its applicable for other platforms as well. Naming it as >> qcom,kaanapali-iris.h would make it look like kaanapali specific. > > I repeated that feedback way too many times. thanks for the feedback. I’ll fix this in next revision. > > NAK > > Nacked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com > > Best regards, > Krzysztof
On 27/02/2026 16:50, Krzysztof Kozlowski wrote: > On 27/02/2026 15:11, Vikash Garodia wrote: >> + >> +maintainers: >> + - Vikash Garodia <vikash.garodia@oss.qualcomm.com> >> + - Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com> >> + >> +description: >> + The iris video processing unit is a video encode and decode accelerator >> + present on Qualcomm Kaanapali SoC. >> + >> +definitions: >> + iommu-types: >> + items: >> + - description: Function ID >> + - description: Phandle to IOMMU >> + - description: IOMMU stream ID base >> + - description: IOMMU stream ID mask >> + - description: Number of stream IDs > > You don't need definitions. Although when iommu-map is properly written listing items, then it would use that. Anyway, we don't use definitions but defs (see git grep). Best regards, Krzysztof
On Fri, 27 Feb 2026 19:41:17 +0530, Vikash Garodia wrote:
> Kaanapali SOC brings in the new generation of video IP i.e iris4. When
> compared to previous generation, iris3x, it has,
> - separate power domains for stream and pixel processing hardware blocks
> (bse and vpp).
> - additional power domain for apv codec.
> - power domains for individual pipes (VPPx).
> - different clocks and reset lines.
>
> iommu-map include all the different stream-ids which can be possibly
> generated by vpu4 hardware as below,
> bitstream stream from vcodec
> non-pixel stream from vcodec
> non-pixel stream from tensilica
> pixel stream from vcodec
> secure bitstream stream from vcodec
> secure non-pixel stream from vcodec
> secure non-pixel stream from tensilica
> secure pixel stream from vcodec
> firmware stream from tensilica (might be handled by the TZ / hyp)
>
> This patch is depend on the below dt-schema patch.
> Link: https://github.com/devicetree-org/dt-schema/pull/184/changes/d341298d62805bc972dfba691da6b3b62aa3ff15
> Signed-off-by: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
> ---
> .../bindings/media/qcom,kaanapali-iris.yaml | 261 +++++++++++++++++++++
> include/dt-bindings/media/qcom,iris.h | 18 ++
> 2 files changed, 279 insertions(+)
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdm845.example.dtb: pcie@1c00000 (qcom,pcie-sdm845): iommu-map:0: [0, 4294967295, 7184, 1, 256, 4294967295, 7185, 1, 512, 4294967295, 7186, 1, 768, 4294967295, 7187, 1, 1024, 4294967295, 7188, 1, 1280, 4294967295, 7189, 1, 1536, 4294967295, 7190, 1, 1792, 4294967295, 7191, 1, 2048, 4294967295, 7192, 1, 2304, 4294967295, 7193, 1, 2560, 4294967295, 7194, 1, 2816, 4294967295, 7195, 1, 3072, 4294967295, 7196, 1, 3328, 4294967295, 7197, 1, 3584, 4294967295, 7198, 1, 3840, 4294967295, 7199, 1] is too long
from schema $id: http://devicetree.org/schemas/pci/qcom,pcie-sdm845.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdm845.example.dtb: pcie@1c00000 (qcom,pcie-sdm845): Unevaluated properties are not allowed ('#address-cells', '#interrupt-cells', '#size-cells', 'bus-range', 'device_type', 'interrupt-map', 'interrupt-map-mask', 'iommu-map', 'linux,pci-domain', 'num-lanes', 'pcie@0', 'perst-gpios', 'phy-names', 'phys', 'power-domains', 'ranges', 'vddpe-3v3-supply', 'wake-gpios' were unexpected)
from schema $id: http://devicetree.org/schemas/pci/qcom,pcie-sdm845.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdm845.example.dtb: pcie@1c00000 (qcom,pcie-sdm845): iommu-map:0: [0, 4294967295, 7184, 1, 256, 4294967295, 7185, 1, 512, 4294967295, 7186, 1, 768, 4294967295, 7187, 1, 1024, 4294967295, 7188, 1, 1280, 4294967295, 7189, 1, 1536, 4294967295, 7190, 1, 1792, 4294967295, 7191, 1, 2048, 4294967295, 7192, 1, 2304, 4294967295, 7193, 1, 2560, 4294967295, 7194, 1, 2816, 4294967295, 7195, 1, 3072, 4294967295, 7196, 1, 3328, 4294967295, 7197, 1, 3584, 4294967295, 7198, 1, 3840, 4294967295, 7199, 1] is too long
from schema $id: http://devicetree.org/schemas/pci/pci-iommu.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdx55.example.dtb: pcie@1c00000 (qcom,pcie-sdx55): iommu-map:0: [0, 4294967295, 512, 1, 256] is too long
from schema $id: http://devicetree.org/schemas/pci/qcom,pcie-sdx55.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdx55.example.dtb: pcie@1c00000 (qcom,pcie-sdx55): iommu-map:1:0: 4294967295 is greater than the maximum of 65535
from schema $id: http://devicetree.org/schemas/pci/qcom,pcie-sdx55.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdx55.example.dtb: pcie@1c00000 (qcom,pcie-sdx55): iommu-map:1: [4294967295, 513, 1, 512, 4294967295] is too long
from schema $id: http://devicetree.org/schemas/pci/qcom,pcie-sdx55.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdx55.example.dtb: pcie@1c00000 (qcom,pcie-sdx55): iommu-map:2:3: 4294967295 is greater than the maximum of 65536
from schema $id: http://devicetree.org/schemas/pci/qcom,pcie-sdx55.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdx55.example.dtb: pcie@1c00000 (qcom,pcie-sdx55): iommu-map:2: [514, 1, 768, 4294967295, 515] is too long
from schema $id: http://devicetree.org/schemas/pci/qcom,pcie-sdx55.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdx55.example.dtb: pcie@1c00000 (qcom,pcie-sdx55): iommu-map:3: [1, 1024, 4294967295, 516, 1] is too long
from schema $id: http://devicetree.org/schemas/pci/qcom,pcie-sdx55.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdx55.example.dtb: pcie@1c00000 (qcom,pcie-sdx55): Unevaluated properties are not allowed ('#address-cells', '#interrupt-cells', '#size-cells', 'bus-range', 'device_type', 'interrupt-map', 'interrupt-map-mask', 'iommu-map', 'linux,pci-domain', 'num-lanes', 'pcie@0', 'perst-gpios', 'phy-names', 'phys', 'power-domains', 'ranges', 'wake-gpios' were unexpected)
from schema $id: http://devicetree.org/schemas/pci/qcom,pcie-sdx55.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdx55.example.dtb: pcie@1c00000 (qcom,pcie-sdx55): iommu-map:0: [0, 4294967295, 512, 1, 256] is too long
from schema $id: http://devicetree.org/schemas/pci/pci-iommu.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdx55.example.dtb: pcie@1c00000 (qcom,pcie-sdx55): iommu-map:1:0: 4294967295 is greater than the maximum of 65535
from schema $id: http://devicetree.org/schemas/pci/pci-iommu.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdx55.example.dtb: pcie@1c00000 (qcom,pcie-sdx55): iommu-map:1: [4294967295, 513, 1, 512, 4294967295] is too long
from schema $id: http://devicetree.org/schemas/pci/pci-iommu.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdx55.example.dtb: pcie@1c00000 (qcom,pcie-sdx55): iommu-map:2:3: 4294967295 is greater than the maximum of 65536
from schema $id: http://devicetree.org/schemas/pci/pci-iommu.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdx55.example.dtb: pcie@1c00000 (qcom,pcie-sdx55): iommu-map:2: [514, 1, 768, 4294967295, 515] is too long
from schema $id: http://devicetree.org/schemas/pci/pci-iommu.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/qcom,pcie-sdx55.example.dtb: pcie@1c00000 (qcom,pcie-sdx55): iommu-map:3: [1, 1024, 4294967295, 516, 1] is too long
from schema $id: http://devicetree.org/schemas/pci/pci-iommu.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.example.dtb: video-codec@2000000 (qcom,kaanapali-iris): iommu-map:0: [256, 4294967295, 6468, 0, 1] is too long
from schema $id: http://devicetree.org/schemas/pci/pci-iommu.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.example.dtb: video-codec@2000000 (qcom,kaanapali-iris): iommu-map:1: [257, 4294967295, 6464, 0, 1] is too long
from schema $id: http://devicetree.org/schemas/pci/pci-iommu.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.example.dtb: video-codec@2000000 (qcom,kaanapali-iris): iommu-map:2: [257, 4294967295, 6688, 0, 1] is too long
from schema $id: http://devicetree.org/schemas/pci/pci-iommu.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.example.dtb: video-codec@2000000 (qcom,kaanapali-iris): iommu-map:3: [258, 4294967295, 6467, 0, 1] is too long
from schema $id: http://devicetree.org/schemas/pci/pci-iommu.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.example.dtb: video-codec@2000000 (qcom,kaanapali-iris): iommu-map:4: [512, 4294967295, 6470, 0, 1] is too long
from schema $id: http://devicetree.org/schemas/pci/pci-iommu.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.example.dtb: video-codec@2000000 (qcom,kaanapali-iris): iommu-map:5: [513, 4294967295, 6465, 0, 1] is too long
from schema $id: http://devicetree.org/schemas/pci/pci-iommu.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.example.dtb: video-codec@2000000 (qcom,kaanapali-iris): iommu-map:6: [513, 4294967295, 6689, 0, 1] is too long
from schema $id: http://devicetree.org/schemas/pci/pci-iommu.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.example.dtb: video-codec@2000000 (qcom,kaanapali-iris): iommu-map:7: [514, 4294967295, 6469, 0, 1] is too long
from schema $id: http://devicetree.org/schemas/pci/pci-iommu.yaml
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/qcom,kaanapali-iris.example.dtb: video-codec@2000000 (qcom,kaanapali-iris): iommu-map:8: [768, 4294967295, 6690, 0, 1] is too long
from schema $id: http://devicetree.org/schemas/pci/pci-iommu.yaml
doc reference errors (make refcheckdocs):
See https://patchwork.kernel.org/project/devicetree/patch/20260227-kaanapali-iris-v2-1-850043ac3933@oss.qualcomm.com
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.
© 2016 - 2026 Red Hat, Inc.