From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Vikash Garodia <quic_vgarodia@quicinc.com>,
Dikshita Agarwal <quic_dikshita@quicinc.com>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] dt-bindings: media: qcom,sm8550-iris: add non_pixel and resv_region properties
Date: Tue, 24 Jun 2025 10:33:00 +0200 [thread overview]
Message-ID: <ea0d8afb-4d64-4fc5-996b-452420e750da@kernel.org> (raw)
In-Reply-To: <2bd17ab5-950c-4260-ae7c-9ba9a6441496@oss.qualcomm.com>
On 20/06/2025 19:27, Konrad Dybcio wrote:
> On 6/20/25 8:39 AM, Krzysztof Kozlowski wrote:
>> On 20/06/2025 08:20, Vikash Garodia wrote:
>>> Existing definition limits the IOVA to an addressable range of 4GiB, and
>>> even within that range, some of the space is used by IO registers,
>>> thereby limiting the available IOVA to even lesser. Video hardware is
>>> designed to emit different stream-ID for pixel and non_pixel buffers,
>>> thereby introduce a non_pixel sub node to handle non_pixel stream-ID.
>>>
>>> With this, both iris and non_pixel device can have IOVA range of 0-4GiB
>>> individually. Certain video usecases like higher video concurrency needs
>>> IOVA higher than 4GiB.
>>>
>>> Add the "resv_region" property, which defines reserved IOVA regions that
>>> are *excluded* from addressable range. Video hardware generates
>>> different stream IDs based on the range of IOVA addresses. Thereby IOVA
>>> addresses for firmware and data buffers need to be non overlapping. For
>>> ex. 0x0-0x25800000 address range is reserved for firmware stream-ID,
>>> while non_pixel (bitstream ) stream-ID can be generated by hardware only
>>> when bitstream buffers IOVA address is from 0x25800000-0xe0000000.
>>>
>>> Signed-off-by: Vikash Garodia <quic_vgarodia@quicinc.com>
>>> ---
>>> .../bindings/media/qcom,sm8550-iris.yaml | 35 ++++++++++++++++++++++
>>> 1 file changed, 35 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/media/qcom,sm8550-iris.yaml b/Documentation/devicetree/bindings/media/qcom,sm8550-iris.yaml
>>> index c79bf2101812d83b99704f38b7348a9f728dff44..a1e83bae3c36f3a4c58b212ef457905e38091b97 100644
>>> --- a/Documentation/devicetree/bindings/media/qcom,sm8550-iris.yaml
>>> +++ b/Documentation/devicetree/bindings/media/qcom,sm8550-iris.yaml
>>> @@ -65,10 +65,45 @@ properties:
>>> - const: core
>>>
>>> iommus:
>>> + minItems: 1
>>
>> As discussed in other patchset, this needs clear explanation, so
>> imperfect patch won't be used in future discussions as argument to take
>> more of such things.
>>
>>> maxItems: 2
>>>
>>> dma-coherent: true
>>>
>>> + resv_region:
>>
>> DTS coding style. Anyway, regions go with memory-region bindings. Use that.
>
> On a tangent, FWIW this is a discussion related to this patchset that
> never got much attention:
>
> https://lore.kernel.org/linux-devicetree/9439182e-3338-4d57-aa02-b621bc9498a3@oss.qualcomm.com/
There is no patchset above, just email describing a problem. It did not
get attention maybe because of usual kernel process: show the code, we
do not have time to comment on every problem or idea.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-06-24 8:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 6:20 [PATCH 0/5] Introduce "non_pixel" sub node within iris video node Vikash Garodia
2025-06-20 6:20 ` [PATCH 1/5] dt-bindings: media: qcom,sm8550-iris: add non_pixel and resv_region properties Vikash Garodia
2025-06-20 6:39 ` Krzysztof Kozlowski
2025-06-20 17:27 ` Konrad Dybcio
2025-06-24 8:33 ` Krzysztof Kozlowski [this message]
2025-06-27 19:51 ` Rob Herring
2025-06-23 10:01 ` Vikash Garodia
2025-06-20 6:41 ` Krzysztof Kozlowski
2025-06-20 21:39 ` Dmitry Baryshkov
2025-06-24 16:11 ` Vikash Garodia
2025-06-20 6:20 ` [PATCH 2/5] media: iris: register and configure non-pixel node as platform device Vikash Garodia
2025-06-20 6:20 ` [PATCH 3/5] media: iris: use np_dev as preferred DMA device in HFI queue management Vikash Garodia
2025-06-20 6:20 ` [PATCH 4/5] media: iris: select appropriate DMA device for internal buffers Vikash Garodia
2025-06-20 6:20 ` [PATCH 5/5] media: iris: configure DMA device for vb2 queue on OUTPUT plane Vikash Garodia
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=ea0d8afb-4d64-4fc5-996b-452420e750da@kernel.org \
--to=krzk@kernel.org \
--cc=abhinav.kumar@linux.dev \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@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=quic_dikshita@quicinc.com \
--cc=quic_vgarodia@quicinc.com \
--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