From: Macpaul Lin <macpaul.lin@mediatek.com>
To: Miles Chen <miles.chen@mediatek.com>
Cc: <bear.wang@mediatek.com>, <devicetree@vger.kernel.org>,
<fparent@baylibre.com>, <krzysztof.kozlowski+dt@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>, <linux-usb@vger.kernel.org>,
<macpaul@gmail.com>, <matthias.bgg@gmail.com>,
<pablo.sun@mediatek.com>, <robh+dt@kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: mediatek: mt8195-demo: fix the memory size of node secmon
Date: Tue, 27 Sep 2022 12:00:28 +0800 [thread overview]
Message-ID: <664f3b7d-d629-5af1-cae4-cb5b638a5da1@mediatek.com> (raw)
In-Reply-To: <20220926070544.13257-1-miles.chen@mediatek.com>
On 9/26/22 15:05, Miles Chen wrote:
> Hi Macpaul,
>
>> The size of device tree node secmon (bl31_secmon_reserved) was
>> incorrect. It should be increased to 2MiB (0x200000).
>
> 192K should work when the patch(6147314aeedc) was accepted.
> Does the trusted-firmware-a get larger now, so we need to
> increase the size to 2MiB?
>
> thanks,
> Miles
When mt8195-demo.dts sent to the upstream, at that time the size of
BL31 was small. Because supported functions and modules in BL31 are
basic sets when the board was under early development stage.
Now BL31 includes more firmwares of coprocessors and maturer functions
so the size has grown bigger in real applications. According to the
value reported by customers, we think reserved 2MiB for BL31 might be
enough for maybe the following 2 or 3 years.
>>
>> The origin setting will cause some abnormal behavior due to
>> trusted-firmware-a and related firmware didn't load correctly.
>> The incorrect behavior may vary because of different software stacks.
>> For example, it will cause build error in some Yocto project because
>> it will check if there was enough memory to load trusted-firmware-a
>> to the reserved memory.
>>
>> Cc: stable@vger.kernel.org # v5.19
>> Fixes: 6147314aeedc ("arm64: dts: mediatek: Add device-tree for MT8195 Demo board")
>> Signed-off-by: Macpaul Lin <macpaul.lin@mediatek.com>
Thanks
Macpaul Lin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-27 4:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 9:16 [PATCH] arm64: dts: mediatek: mt8195-demo: fix the memory size of node secmon Macpaul Lin
2022-09-26 7:05 ` Miles Chen
2022-09-27 4:00 ` Macpaul Lin [this message]
2022-09-28 1:47 ` [PATCH] arm64: dts: mediatek: mt8195-demo: fix the memory size of Miles Chen
2022-09-29 8:47 ` [PATCH v2] arm64: dts: mediatek: mt8195-demo: fix the memory size of node secmon Macpaul Lin
2022-10-24 6:18 ` Macpaul Lin
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=664f3b7d-d629-5af1-cae4-cb5b638a5da1@mediatek.com \
--to=macpaul.lin@mediatek.com \
--cc=bear.wang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=fparent@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=macpaul@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=miles.chen@mediatek.com \
--cc=pablo.sun@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=stable@vger.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).