From: Jonathan Marek <jonathan@marek.ca>
To: Bjorn Andersson <andersson@kernel.org>, linux-arm-msm@vger.kernel.org
Cc: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sibi Sankar <sibi.sankar@oss.qualcomm.com>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Abel Vesa <abelvesa@kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: x1e: bus is 40-bits (fix 64GB models)
Date: Fri, 16 Jan 2026 17:53:59 -0500 [thread overview]
Message-ID: <79b3e8ae-134c-df6d-396d-9b7f766ef666@marek.ca> (raw)
In-Reply-To: <176859948742.425550.1764024067188709567.b4-ty@kernel.org>
It turns out this change will make things worse for the (unfortunately
common) EL1+64GB+brokenfirmware case.
Because of that I think the Fixes: tag and "(fix 64GB models)" should be
dropped from the commit message. (I can also send a v2 with extra info
in the commit message if needed)
On 1/16/26 4:39 PM, Bjorn Andersson wrote:
>
> On Thu, 27 Nov 2025 16:29:42 -0500, Jonathan Marek wrote:
>> Unlike the phone SoCs this was copied from, x1e has a 40-bit physical bus.
>> The upper address space is used to support more than 32GB of memory.
>>
>> This fixes issues when DMA buffers are allocated outside the 36-bit range.
>>
>>
>
> Applied, thanks!
>
> [1/1] arm64: dts: qcom: x1e: bus is 40-bits (fix 64GB models)
> commit: b38dd256e11a4c8bd5a893e11fc42d493939c907
>
> Best regards,
>
next prev parent reply other threads:[~2026-01-16 22:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 21:29 [PATCH] arm64: dts: qcom: x1e: bus is 40-bits (fix 64GB models) Jonathan Marek
2025-11-28 10:26 ` Stephan Gerhold
2025-11-28 10:52 ` Konrad Dybcio
2025-11-28 14:49 ` Jonathan Marek
2025-12-01 13:40 ` Konrad Dybcio
2025-11-28 14:39 ` Jonathan Marek
2025-11-28 16:03 ` Stephan Gerhold
2025-11-28 16:34 ` Jonathan Marek
2025-11-28 22:10 ` Christopher Obbard
2025-11-28 22:39 ` Christopher Obbard
2025-11-28 23:56 ` Jonathan Marek
2025-12-01 0:13 ` Steev Klimaszewski
2025-12-01 2:06 ` Jonathan Marek
2025-12-01 2:25 ` Steev Klimaszewski
2026-01-16 21:39 ` Bjorn Andersson
2026-01-16 22:53 ` Jonathan Marek [this message]
2026-01-16 23:19 ` Bjorn Andersson
2026-01-16 23:45 ` Jonathan Marek
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=79b3e8ae-134c-df6d-396d-9b7f766ef666@marek.ca \
--to=jonathan@marek.ca \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_rjendra@quicinc.com \
--cc=robh@kernel.org \
--cc=sibi.sankar@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