From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Vikash Garodia <vikash.garodia@oss.qualcomm.com>
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>,
Stanimir Varbanov <stanimir.varbanov@linaro.org>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Vishnu Reddy <busanna.reddy@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v7 00/12] media: iris: Migrate iommus to iris sub nodes
Date: Sun, 22 Nov 2026 17:42:40 +0100 [thread overview]
Message-ID: <179536576019.207250.7528913659904362125.b4-reply@b4> (raw)
In-Reply-To: <20261120-vpu_iommu_iova_handling-v7-0-25a771235a7f@oss.qualcomm.com>
On 2026-11-20 16:40 +0530, Vikash Garodia wrote:
> The VPU issues DMA through several SMMU streams, and the hardware does
> not restricts specific streams with specific addressable range. The
> non-pixel stream is restricted to use 0-600MB of IOVA space, while the
> pixel stream can address the full range:
> +-----------------------------------------------------------+
> | non-pixel stream addressable range (600 MB - 3.5 GB) |
> | 0x25800000 - 0xe0000000 |
> +-----------------------------------------------------------+
> | pixel stream addressable range (0 - 3.5 GB) |
> | 0x00000000 - 0xe0000000 |
> +-----------------------------------------------------------+
>
> A single "iommus" property on the video-codec node puts every stream in
> one IOMMU domain sharing one IOVA allocator, so nothing keeps a
> non-pixel buffer inside the low 600 MB. Once an allocation lands below
> that boundary the hardware faults, which shows up as unhandled SMMU page
> faults and spontaneous reboots:
> https://gitlab.freedesktop.org/drm/msm/-/work_items/100
>
> Fix was made in iris/venus driver to reserve the 0-600MB range and
> thereby prevent iova allocation from that range.
> https://lore.kernel.org/all/20260818-reserve_iova_in_driver-v2-0-5005a1154408@oss.qualcomm.com
>
> Given that the address range restriction is for specific VPU stream, it
> should be ideally moved to that stream. To achieve the same, a subset
> of streams is now represented as subnodes, so that each can be
> associated with its respective addressable range.
Patchset does not apply, neither on next nor on provided base. At least
b4 review fails here. It seems that pieces of the code here might be
not complete and there are followups, so merge these follow ups here.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-11-22 16:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 11:10 Vikash Garodia
2026-11-20 11:10 ` [PATCH v7 01/12] dt-bindings: media: qcom,venus: Add context bank subnodes to common schema Vikash Garodia
2026-11-20 11:10 ` [PATCH v7 02/12] dt-bindings: media: qcom,sm8550-iris: Add context bank subnodes Vikash Garodia
2026-11-20 11:10 ` [PATCH v7 03/12] dt-bindings: media: qcom,sm8750-iris: " Vikash Garodia
2026-11-20 11:10 ` [PATCH v7 04/12] media: iris: Add non-pixel and pixel context bank devices Vikash Garodia
2026-11-20 11:10 ` [PATCH v7 05/12] media: iris: Route buffers to the matching context bank device Vikash Garodia
2026-11-20 11:10 ` [PATCH v7 06/12] media: iris: Skip DMA mask setup when the core device has no IOMMU Vikash Garodia
2026-11-20 11:10 ` [PATCH v7 07/12] arm64: dts: qcom: hamoa: Add Iris context bank subnodes Vikash Garodia
2026-11-20 11:10 ` [PATCH v7 08/12] arm64: dts: qcom: sm8550: " Vikash Garodia
2026-11-20 11:10 ` [PATCH v7 09/12] arm64: dts: qcom: lemans: " Vikash Garodia
2026-11-20 11:11 ` [PATCH v7 10/12] arm64: dts: qcom: monaco: " Vikash Garodia
2026-11-20 11:11 ` [PATCH v7 11/12] arm64: dts: qcom: sm8650: " Vikash Garodia
2026-11-20 11:11 ` [PATCH v7 12/12] arm64: dts: qcom: sm8750: " Vikash Garodia
2026-11-22 16:42 ` Krzysztof Kozlowski [this message]
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=179536576019.207250.7528913659904362125.b4-reply@b4 \
--to=krzysztof.kozlowski@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=abhinav.kumar@linux.dev \
--cc=andersson@kernel.org \
--cc=bod@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=busanna.reddy@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@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 \
--cc=stanimir.varbanov@linaro.org \
--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
all inboxes | Powered by JetHome®