From: Caleb Connolly <caleb.connolly@linaro.org>
To: Amit Pundir <amit.pundir@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: Split sdm845-db845c to add headless support
Date: Tue, 6 Jun 2023 10:32:20 +0100 [thread overview]
Message-ID: <858eacff-c97d-6504-06c8-d7586055e142@linaro.org> (raw)
In-Reply-To: <20230605094710.2037879-1-amit.pundir@linaro.org>
On 05/06/2023 10:47, Amit Pundir wrote:
> This is a follow-up of the upstream discussion,
> https://lore.kernel.org/linux-kernel/20230124182857.1524912-1-amit.pundir@linaro.org/T/#u,
> around adding a reserved memory region in sdm845-db845c
> for the framebuffer memory (the splash region set up by
> the bootloader) but the general opinion was to avoid
> adding that reserved memory for the headless DB845c
> usecase.
>
> So this patch splits the sdm845-db845c into a common dtsi,
> a new sdm845-db845-headless DT, which disables the mdss
> display subsystem, and a new sdm845-db845c DT with an
> additional reserved-memory region for the framebuffer.
The bootloader always sets up this memory region, it's defined in XBL.
If someone is building a product based on db845c SoM they would need to
modify XBL to free up this memory, at that point I think a new DT would
make sense.
Given that we only found that this was missing because the kernel
randomly allocated memory there and it broke things, marking the region
as reserved is a fix, not reserving it is a bug.
The original patch makes sense, imo this region should go in sdm845.dtsi
as almost all devices utilise this.
I have a pair of patches [1][2] to fix this on sdm845 and sdm850, but I
haven't sent them yet as there doesn't seem to be a consensus on this.
Would this be ok with everyone given the above?
[1]:
https://gitlab.com/sdm845-mainline/linux/-/commit/784f04850b56238c63c30dfea400c7a9ea8fda97
[2]:
https://gitlab.com/sdm845-mainline/linux/-/commit/52f7ac40c6524be0edad5f4416ed76dbf3298dab
>
> The default sdm845-db845c.dtb remains pretty much the same
> (with an exception of additional reserved-memory region),
> while others can use sdm845-db845c-headless.dtb for their
> headless systems.
>
> Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
next prev parent reply other threads:[~2023-06-06 9:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 9:47 [PATCH] arm64: dts: qcom: Split sdm845-db845c to add headless support Amit Pundir
2023-06-05 10:23 ` Stephan Gerhold
2023-06-05 10:37 ` Krzysztof Kozlowski
2023-06-06 6:11 ` Amit Pundir
2023-06-06 6:18 ` Krzysztof Kozlowski
2023-06-06 9:32 ` Caleb Connolly [this message]
2023-06-06 10:15 ` Bryan O'Donoghue
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=858eacff-c97d-6504-06c8-d7586055e142@linaro.org \
--to=caleb.connolly@linaro.org \
--cc=agross@kernel.org \
--cc=amit.pundir@linaro.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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