Linux Media Controller development
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bod@kernel.org>
To: Val Packett <val@packett.cool>,
	Daniel J Blueman <daniel@quora.org>,
	Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
	Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>,
	Abhinav Kumar <abhinav.kumar@linux.dev>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: hamoa: Reserve low IOVA range for Iris
Date: Tue, 2 Jun 2026 16:33:06 +0100	[thread overview]
Message-ID: <d09da32c-5c87-473e-8f02-74bd6e165f46@kernel.org> (raw)
In-Reply-To: <809635d9-6e66-4ace-8f47-4a5a268f4f18@packett.cool>

On 02/06/2026 16:03, Val Packett wrote:
> 
> On 6/2/26 7:26 AM, Bryan O'Donoghue wrote:
>> On 01/06/2026 05:13, Daniel J Blueman wrote:
>>> On X1-family hamoa platforms, Iris DMA below IOVA 0x25800000 (600MB)
>>> triggers unhandled SMMU page faults
>>
>> How do we know that is a correct address - does it come from qcom
>> documentation or trial and error ?
> 
> 
> If you follow the Link:, you can see that it does come from qcom..
> 
> https://github.com/qualcomm-linux/kernel-topics/issues/1157#issuecomment-4458933574

A rhetorical and leading question - the commit log should just explain 
what is going on..

> This series is basically a "hotfix" version of a more complicated series:
> 
> https://lore.kernel.org/linux-media/20250627-video_cb-v3-0-51e18c0ffbce@quicinc.com/


> that introduced an extra subnode that let the driver only use that
> restricted IOVA range for non-pixel buffers (only those actually need
> the restriction) but that resulted in a very long discussion and was
> kinda shelved because of that.. x_x
This and the subsequent require a Fixes:

I think this change is OK wrt to bindings because we are adding not 
subtracting - but I'd like the commit log to actually explain whats 
happening not give me links to random places.

---
bod

  reply	other threads:[~2026-06-02 15:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01  4:13 [PATCH 1/2] dt-bindings: media: qcom,sm8550-iris: Allow IOVA reservation memory-region Daniel J Blueman
2026-06-01  4:13 ` [PATCH 2/2] arm64: dts: qcom: hamoa: Reserve low IOVA range for Iris Daniel J Blueman
2026-06-02 10:26   ` Bryan O'Donoghue
2026-06-02 15:03     ` Val Packett
2026-06-02 15:33       ` Bryan O'Donoghue [this message]
2026-06-02 15:35     ` Daniel J Blueman
2026-06-04  6:38       ` Vikash Garodia
2026-06-08  3:48         ` Val Packett
2026-06-08  4:17           ` Xilin Wu
2026-06-08 13:36           ` Bryan O'Donoghue
2026-06-09 13:01         ` Bryan O'Donoghue
2026-07-10 10:51           ` Bryan O'Donoghue
2026-06-10  1:14         ` Daniel J Blueman
2026-06-01  4:27 ` [PATCH 1/2] dt-bindings: media: qcom,sm8550-iris: Allow IOVA reservation memory-region sashiko-bot
2026-06-01 17:45 ` Rob Herring (Arm)
2026-06-04 19:15 ` Frank Li

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=d09da32c-5c87-473e-8f02-74bd6e165f46@kernel.org \
    --to=bod@kernel.org \
    --cc=abhinav.kumar@linux.dev \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=daniel@quora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dikshita.agarwal@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=stable@vger.kernel.org \
    --cc=val@packett.cool \
    --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