[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7f4a7739-cb03-bda8-df90-e8eb119b732b@arm.com>
Date: Thu, 27 Jul 2023 15:57:59 +0100
From: Andre Przywara <andre.przywara@....com>
To: Andrey Skvortsov <andrej.skvortzov@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Chen-Yu Tsai <wens@...e.org>,
Jernej Skrabec <jernej.skrabec@...il.com>,
Samuel Holland <samuel@...lland.org>,
Kees Cook <keescook@...omium.org>,
Tony Luck <tony.luck@...el.com>,
"Guilherme G. Piccoli" <gpiccoli@...lia.com>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-sunxi@...ts.linux.dev, linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org,
Jarrah Gosbell <kernel@...ef.tools>,
Arnaud Ferraris <arnaud.ferraris@...labora.com>
Subject: Re: [PATCH] arm64: dts: pinephone: Add pstore support for PinePhone
A64
Hi,
On 24/07/2023 22:34, Andrey Skvortsov wrote:
> This patch reserves some memory in the DTS and sets up a
> pstore device tree node to enable pstore support.
>
> Signed-off-by: Andrey Skvortsov <andrej.skvortzov@...il.com>
>
> Gbp-Pq: Topic pinephone
> Gbp-Pq: Name 0161-arm64-dts-pinephone-Add-pstore-support-for-PinePhone.patch
> ---
> .../boot/dts/allwinner/sun50i-a64-pinephone.dtsi | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-pinephone.dtsi b/arch/arm64/boot/dts/allwinner/sun50i-a64-pinephone.dtsi
> index 87847116ab6d..84f9410b0b70 100644
> --- a/arch/arm64/boot/dts/allwinner/sun50i-a64-pinephone.dtsi
> +++ b/arch/arm64/boot/dts/allwinner/sun50i-a64-pinephone.dtsi
> @@ -19,6 +19,22 @@ aliases {
> serial0 = &uart0;
> };
>
> + reserved-memory {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges;
> +
> + pstore_mem: ramoops@...00000 {
> + compatible = "ramoops";
> + reg = <0x61000000 0x100000>;
So what's the significance of this address? That's 528MB into DRAM, so
somewhat in the middle of it, fragmenting the physical address space.
And is there any other firmware component that needs to know about this
address?
Cheers,
Andre
> + record-size = <0x20000>;
> + console-size = <0x20000>;
> + ftrace-size = <0x20000>;
> + pmsg-size = <0x20000>;
> + ecc-size = <16>;
> + };
> + };
> +
> backlight: backlight {
> compatible = "pwm-backlight";
> pwms = <&r_pwm 0 50000 PWM_POLARITY_INVERTED>;
Powered by blists - more mailing lists