From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Stephan Gerhold <stephan@gerhold.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
devicetree@vger.kernel.org, devicetree-spec@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/5] of: reserved_mem: Provide more control about allocation behavior
Date: Wed, 17 May 2023 21:25:36 +0200 [thread overview]
Message-ID: <c28494ec-1eb3-239e-46d8-fe84c2f28e77@linaro.org> (raw)
In-Reply-To: <20230510-dt-resv-bottom-up-v1-0-3bf68873dbed@gerhold.net>
On 15.05.2023 12:12, Stephan Gerhold wrote:
> Provide more control about the allocation behavior for dynamically
> allocated reserved memory by adding a "alloc-bottom-up" and
> "alloc-top-down" option and by making the allocation order
> deterministic.
>
> The motivation for this patch series are the many different reserved
> firmware regions on Qualcomm platforms. Currently it is often necessary
> to duplicate them into each board DT, because minor differences for
> some of the firmware regions (e.g. the firmware size) requires shifting
> the base address of all following firmware regions as well.
>
> I propose describing the actual requirements (size, alignment,
> alloc-ranges) instead and allocating the reserved regions at runtime.
> This allows defining only the actual device-specific part in the board
> DT and having everything else shared in the SoC.dtsi.
>
> The series starts with two minor additions to the of_reserved_mem code.
> The last two patches are examples that are meant to show the motivation
> more clearly for the MSM8916 SoC. PATCH 4/5 shows the current (static)
> approach, then PATCH 5/5 switches to the dynamic allocation based on
> the first 3 patches.
>
> If the first 3 patches are accepted I would send the full MSM8916 DT
> changes in a separate series.
>
> Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> ---
Sounds great!
Konrad
> Stephan Gerhold (5):
> dt-bindings: reserved-memory: Add alloc-{bottom-up,top-down}
> of: reserved_mem: Implement alloc-{bottom-up,top-down}
> of: reserved_mem: Use stable allocation order
> [RFC] arm64: dts: qcom: msm8916: Enable modem on two phones
> [RFC] arm64: dts: qcom: msm8916: Reserve firmware memory dynamically
>
> .../bindings/reserved-memory/reserved-memory.yaml | 39 ++++++++++++++++++++
> arch/arm64/boot/dts/qcom/apq8016-sbc.dts | 13 +++++++
> .../boot/dts/qcom/msm8916-longcheer-l8150.dts | 31 ++++++++++++++--
> .../boot/dts/qcom/msm8916-samsung-serranove.dts | 21 +++++++++++
> arch/arm64/boot/dts/qcom/msm8916-ufi.dtsi | 29 ++++++++-------
> arch/arm64/boot/dts/qcom/msm8916.dtsi | 42 ++++++++++++++++------
> drivers/of/of_reserved_mem.c | 14 +++++++-
> 7 files changed, 163 insertions(+), 26 deletions(-)
> ---
> base-commit: 715abedee4cd660ad390659aefa7482f05275bbd
> change-id: 20230510-dt-resv-bottom-up-68d71ff6628f
>
> Best regards,
prev parent reply other threads:[~2023-05-17 19:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 10:12 [PATCH 0/5] of: reserved_mem: Provide more control about allocation behavior Stephan Gerhold
2023-05-15 10:12 ` [PATCH 1/5] dt-bindings: reserved-memory: Add alloc-{bottom-up,top-down} Stephan Gerhold
2023-06-08 14:02 ` Rob Herring
2023-06-09 9:16 ` Stephan Gerhold
2023-06-13 13:33 ` Rob Herring
2023-05-15 10:12 ` [PATCH 2/5] of: reserved_mem: Implement alloc-{bottom-up,top-down} Stephan Gerhold
2023-05-17 19:28 ` Konrad Dybcio
2023-05-15 10:12 ` [PATCH 3/5] of: reserved_mem: Use stable allocation order Stephan Gerhold
2023-05-15 10:12 ` [PATCH RFC 4/5] arm64: dts: qcom: msm8916: Enable modem on two phones Stephan Gerhold
2023-05-15 10:12 ` [PATCH RFC 5/5] arm64: dts: qcom: msm8916: Reserve firmware memory dynamically Stephan Gerhold
2023-05-17 19:25 ` Konrad Dybcio [this message]
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=c28494ec-1eb3-239e-46d8-fe84c2f28e77@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=stephan@gerhold.net \
/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).