From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sumit Garg <sumit.garg@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
akhilpo@oss.qualcomm.com, vikash.garodia@oss.qualcomm.com,
dikshita.agarwal@oss.qualcomm.com, robin.clark@oss.qualcomm.com,
lumag@kernel.org, loic.poulain@oss.qualcomm.com,
jorge.ramirez@oss.qualcomm.com, linux-kernel@vger.kernel.org,
Sumit Garg <sumit.garg@oss.qualcomm.com>
Subject: Re: [PATCH v2 2/3] media: dt-bindings: venus: Fix iommus property
Date: Fri, 16 Jan 2026 09:47:37 +0100 [thread overview]
Message-ID: <20260116-burrowing-weightless-sawfly-53dc98@quoll> (raw)
In-Reply-To: <20260116062004.237356-3-sumit.garg@kernel.org>
On Fri, Jan 16, 2026 at 11:50:03AM +0530, Sumit Garg wrote:
> From: Sumit Garg <sumit.garg@oss.qualcomm.com>
>
> Fix IOMMU DT propety for venus via dropping SMMU stream IDs which
> relates to secure context bank. Assigning Linux kernel (HLOS) VMID
> to secure context bank stream IDs is incorrect.
>
> The min value is added for iommus property to ensure in future when
You do not add min value (that would be "minimum") but change the list.
> secure context bank stream IDs are properly supported then the iommus
> property is extensible.
>
> These DT bindings changes should be backwards compatible.
>
> Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
> ---
> .../devicetree/bindings/media/qcom,qcm2290-venus.yaml | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/media/qcom,qcm2290-venus.yaml b/Documentation/devicetree/bindings/media/qcom,qcm2290-venus.yaml
> index 3f3ee82fc878..ae6bc0d0bea6 100644
> --- a/Documentation/devicetree/bindings/media/qcom,qcm2290-venus.yaml
> +++ b/Documentation/devicetree/bindings/media/qcom,qcm2290-venus.yaml
> @@ -42,6 +42,7 @@ properties:
> - const: vcodec0_bus
>
> iommus:
> + minItems: 2
Same problem.
> maxItems: 5
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-16 8:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 6:20 [PATCH v2 0/3] arm64: dts: qcom: agatti: Fix IOMMU DT properties Sumit Garg
2026-01-16 6:20 ` [PATCH v2 1/3] dt-bindings: display: msm: qcm2290-mdss: Fix iommus property Sumit Garg
2026-01-16 8:46 ` Krzysztof Kozlowski
2026-01-16 12:53 ` Sumit Garg
2026-01-16 13:15 ` Krzysztof Kozlowski
2026-01-20 12:16 ` Sumit Garg
2026-01-20 12:30 ` Krzysztof Kozlowski
2026-01-21 7:59 ` Sumit Garg
2026-01-16 6:20 ` [PATCH v2 2/3] media: dt-bindings: venus: " Sumit Garg
2026-01-16 8:47 ` Krzysztof Kozlowski [this message]
2026-01-16 6:20 ` [PATCH v2 3/3] arm64: dts: qcom: agatti: Fix IOMMU DT properties Sumit Garg
2026-01-16 8:40 ` Dmitry Baryshkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260116-burrowing-weightless-sawfly-53dc98@quoll \
--to=krzk@kernel.org \
--cc=akhilpo@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=jorge.ramirez@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=lumag@kernel.org \
--cc=robh@kernel.org \
--cc=robin.clark@oss.qualcomm.com \
--cc=sumit.garg@kernel.org \
--cc=sumit.garg@oss.qualcomm.com \
--cc=vikash.garodia@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox