Message ID | 20220126044954.19069-1-christianshewitt@gmail.com |
---|---|
Headers | show |
Series | arm64: dts: meson: add ATF BL32 reserved-memory regions | expand |
> On 26 Jan 2022, at 9:35 am, Vyacheslav <adeep@lexina.in> wrote: > > Hi! > > 26.01.2022 07:49, Christian Hewitt wrote: >> Add an additional reserved memory region for the BL32 trusted firmware >> present in many devices that boot from Amlogic vendor u-boot. >> Suggested-by: Mateusz Krzak <kszaquitto@gmail.com> >> Signed-off-by: Christian Hewitt <christianshewitt@gmail.com> >> --- >> arch/arm64/boot/dts/amlogic/meson-gx.dtsi | 6 ++++++ >> 1 file changed, 6 insertions(+) >> diff --git a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi >> index 6b457b2c30a4..aa14ea017a61 100644 >> --- a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi >> +++ b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi >> @@ -49,6 +49,12 @@ >> no-map; >> }; >> + /* 32 MiB reserved for ARM Trusted Firmware (BL32) */ >> + secmon_reserved_bl32: secmon@5300000 { >> + reg = <0x0 0x05300000 0x0 0x2000000>; >> + no-map; >> + }; >> + > How do I check if we need a similar patch for axg boards? Are they booting using Amlogic (vendor) u-boot sources that include bl32.img in the FIP signing recipe? If booting from upstream u-boot, like JetHome boards, it’s nothing to worry about. Christian
On 26/01/2022 05:49, Christian Hewitt wrote: > Add an additional reserved memory region for the BL32 trusted firmware > present in many devices that boot from Amlogic vendor u-boot. > > Suggested-by: Mateusz Krzak <kszaquitto@gmail.com> > Signed-off-by: Christian Hewitt <christianshewitt@gmail.com> > --- > arch/arm64/boot/dts/amlogic/meson-gx.dtsi | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi > index 6b457b2c30a4..aa14ea017a61 100644 > --- a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi > +++ b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi > @@ -49,6 +49,12 @@ > no-map; > }; > > + /* 32 MiB reserved for ARM Trusted Firmware (BL32) */ > + secmon_reserved_bl32: secmon@5300000 { > + reg = <0x0 0x05300000 0x0 0x2000000>; > + no-map; > + }; > + > linux,cma { > compatible = "shared-dma-pool"; > reusable; > Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
Christian Hewitt <christianshewitt@gmail.com> writes: > This series supersedes [0] which fixed a long-running kernel panic issue > seen with Beelink G12B devices booted from Amlogic vendor firmware. The > same issue exists with a wider set of devices from GXBB to SM1, although > it is not often seen due to my kernel fork including 'catch-all' patches > for some time (the meson-gx patch was suggested by Matheusz in 2019) and > many distros actively supporting Amlogic hardware consuming some or all > of my regular patchset. > > I've also included a cleanup to the SEI510/SEI610 board files. If that's > not desirable feel free to ignore that patch. I also dropped the fixes > tagging as I'm not sure what original commits could be targetted. If you > think fixes are good please provide some guidance and I'll be happy to > send a revised series. Reviewed-by: Kevin Hilman <khilman@baylibre.com>