From: Bryan O'Donoghue <bod@kernel.org>
To: Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
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>
Cc: linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v3 2/3] arm64: dts: qcom: shikra: Add Iris video codec node
Date: Mon, 22 Jun 2026 12:20:54 +0100 [thread overview]
Message-ID: <63dfb417-323d-4397-b95b-8c655be38129@kernel.org> (raw)
In-Reply-To: <20260618-shikra_vpu-v3-2-1a32e26a35a1@oss.qualcomm.com>
On 18/06/2026 11:39, Vikash Garodia wrote:
> + memory-region = <&video_mem>;
I'll reiterate, again...
Since we know there is a problem with non-pixel allocations < 600 MB,
submission _must_ address that.
Its irrelevant that something upstream already does the wrong thing.
Please fix this.
---
bod
next prev parent reply other threads:[~2026-06-22 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 10:39 [PATCH v3 0/3] media: qcom: Add support for the iris codec on shikra Vikash Garodia
2026-06-18 10:39 ` [PATCH v3 1/3] dt-bindings: media: qcom,qcm2290-venus: document shikra Iris compatible Vikash Garodia
2026-06-19 3:38 ` Vishnu Reddy
2026-06-22 9:24 ` Krzysztof Kozlowski
2026-06-22 11:23 ` Bryan O'Donoghue
2026-06-18 10:39 ` [PATCH v3 2/3] arm64: dts: qcom: shikra: Add Iris video codec node Vikash Garodia
2026-06-19 4:38 ` Vishnu Reddy
2026-06-22 11:20 ` Bryan O'Donoghue [this message]
2026-06-18 10:39 ` [PATCH v3 3/3] arm64: dts: qcom: shikra-evk: Enable Iris core Vikash Garodia
2026-06-19 4:48 ` Vishnu Reddy
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=63dfb417-323d-4397-b95b-8c655be38129@kernel.org \
--to=bod@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jorge.ramirez@oss.qualcomm.com \
--cc=konrad.dybcio@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=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.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