From: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Bryan O'Donoghue <bod@kernel.org>,
Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jorge Ramirez-Ortiz <jorge.ramirez@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: media: qcom,qcm2290-venus: document shikra Iris compatible
Date: Wed, 10 Jun 2026 23:38:37 +0530 [thread overview]
Message-ID: <5e1be8c3-3e41-4a4f-bb70-3bc6bad7f26d@oss.qualcomm.com> (raw)
In-Reply-To: <20260610-flexible-badger-of-dignity-bbaea0@quoll>
On 6/10/2026 2:47 PM, Krzysztof Kozlowski wrote:
> On Tue, Jun 09, 2026 at 09:45:40PM +0530, Vikash Garodia wrote:
>> Document the iris video accelerator used on shikra platforms by adding
>> the qcom,shikra-iris compatible.
>>
>> Although QCM2290 and shikra share the same video hardware and overall
>> integration, their SMMU programming differs. QCM2290 exposes separate
>> stream IDs for the video hardware and the Xtensa path, requiring two
>> explicit IOMMU entries, whereas shikra uses a masked SMR to collapse
>> equivalent stream IDs into a single mapping. Due to QCM2290’s SID layout
>> and Xtensa isolation requirements, such SMR masking is not applicable on
>> QCM2290 platforms.
>> Since shikra uses the same video hardware as QCM2290 and shares the same
>> programming model and capabilities, it is added as a fallback compatible
>> to qcom,qcm2290-venus, with conditional handling to allow either one or
>> two IOMMU entries.
>>
>> Signed-off-by: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
>> ---
>> .../bindings/media/qcom,qcm2290-venus.yaml | 20 ++++++++++++++++----
>> 1 file changed, 16 insertions(+), 4 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/media/qcom,qcm2290-venus.yaml b/Documentation/devicetree/bindings/media/qcom,qcm2290-venus.yaml
>> index 5977e7d0a71b4fb5681f1c2094439c251366f01f..895533b9756690d075fd7729e3f805c8e72ff0df 100644
>> --- a/Documentation/devicetree/bindings/media/qcom,qcm2290-venus.yaml
>> +++ b/Documentation/devicetree/bindings/media/qcom,qcm2290-venus.yaml
>> @@ -15,12 +15,27 @@ description:
>>
>> allOf:
>> - $ref: qcom,venus-common.yaml#
>> + - if:
>> + properties:
>> + compatible:
>> + contains:
>> + const: qcom,shikra-iris
>> + then:
>> + properties:
>> + iommus:
>> + maxItems: 1
>> + else:
>> + properties:
>> + iommus:
>> + maxItems: 2
>
> allOf goes to the end, after required: block. See example-schema.
>
Ack
>
>>
>> properties:
>> compatible:
>> oneOf:
>> - items:
>> - - const: qcom,sm6115-venus
>> + - enum:
>> + - qcom,sm6115-venus
>> + - qcom,shikra-iris
>
> Messed order.
>
Ack
>> - const: qcom,qcm2290-venus
>> - const: qcom,qcm2290-venus
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2026-06-10 18:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 16:15 [PATCH 0/3] media: qcom: Add support for the iris codec on shikra Vikash Garodia
2026-06-09 16:15 ` [PATCH 1/3] dt-bindings: media: qcom,qcm2290-venus: document shikra Iris compatible Vikash Garodia
2026-06-09 20:37 ` Bryan O'Donoghue
2026-06-10 7:50 ` Vikash Garodia
2026-06-10 8:54 ` Bryan O'Donoghue
2026-06-10 9:05 ` Vikash Garodia
2026-06-12 7:49 ` Dmitry Baryshkov
2026-06-15 6:00 ` Vikash Garodia
2026-06-10 9:17 ` Krzysztof Kozlowski
2026-06-10 18:08 ` Vikash Garodia [this message]
2026-06-09 16:15 ` [PATCH 2/3] arm64: dts: qcom: shikra: Add Iris video codec node Vikash Garodia
2026-06-09 22:28 ` Dmitry Baryshkov
2026-06-10 9:15 ` Konrad Dybcio
2026-06-09 16:15 ` [PATCH 3/3] arm64: dts: qcom: shikra-evk: Enable Iris core Vikash Garodia
2026-06-09 22:26 ` 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=5e1be8c3-3e41-4a4f-bb70-3bc6bad7f26d@oss.qualcomm.com \
--to=vikash.garodia@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bod@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=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
/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