From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Amit Pundir <amit.pundir@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Caleb Connolly <caleb.connolly@linaro.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
dt <devicetree@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as reserved
Date: Thu, 9 Feb 2023 13:32:30 +0100 [thread overview]
Message-ID: <76311e72-0e18-d6b7-6dfc-a312e930e095@linaro.org> (raw)
In-Reply-To: <027268b7-4b04-f52e-06a8-9d924dc6efe4@linaro.org>
On 9.02.2023 13:22, Bryan O'Donoghue wrote:
> On 09/02/2023 12:11, Bryan O'Donoghue wrote:
>>> If the bootloader splash is enabled then this memory is used until the
>>> DPU driver instructs MDP5 pipes to suck data from a newly assigned address,
>>> so there's a short window where it is.
>>
>> It seems a shame to reserve 30 something megabytes of memory for continuous splash unless we are actually using it is my point.
>>
>> If I'm running headless its just wasted memory.
>
> Couldn't we
>
> 1. Find reserved continuous splash memory
> 2. Fee it in the MDP when we make the transition
>
> It must be possible
I suppose we could mark it as shared-dma-pool, pass it to
MDSS, reserve it from there (by occupying the whole thing)
and either use it or free it before jumping to the newly
allocated region.
The MDSS driver can already accept it through memory-region = <>
IIRC, but *nobody* uses that, so I'm not sure it even still works..
Konrad
>
> ---
> bod
next prev parent reply other threads:[~2023-02-09 12:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 18:28 [PATCH] arm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as reserved Amit Pundir
2023-01-31 10:46 ` Caleb Connolly
2023-01-31 10:54 ` Bryan O'Donoghue
2023-01-31 11:06 ` Dmitry Baryshkov
2023-01-31 12:45 ` Konrad Dybcio
2023-01-31 13:33 ` Dmitry Baryshkov
2023-02-09 9:05 ` Amit Pundir
2023-02-09 11:03 ` Bryan O'Donoghue
2023-02-09 12:08 ` Konrad Dybcio
2023-02-09 12:11 ` Bryan O'Donoghue
2023-02-09 12:22 ` Bryan O'Donoghue
2023-02-09 12:32 ` Konrad Dybcio [this message]
2023-02-09 13:54 ` Dmitry Baryshkov
2023-04-10 8:51 ` Amit Pundir
2023-04-10 8:54 ` Amit Pundir
2023-04-10 12:44 ` 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=76311e72-0e18-d6b7-6dfc-a312e930e095@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=amit.pundir@linaro.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=caleb.connolly@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@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;
as well as URLs for NNTP newsgroup(s).