From: Andrey Skvortsov <andrej.skvortzov@gmail.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: "Jernej Škrabec" <jernej.skrabec@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Chen-Yu Tsai" <wens@csie.org>,
"Samuel Holland" <samuel@sholland.org>,
"Kees Cook" <keescook@chromium.org>,
"Tony Luck" <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org,
"Jarrah Gosbell" <kernel@undef.tools>,
"Arnaud Ferraris" <arnaud.ferraris@collabora.com>,
"Pavel Machek" <pavel@ucw.cz>
Subject: Re: [PATCH v2] arm64: dts: pinephone: Add pstore support for PinePhone A64
Date: Fri, 25 Aug 2023 13:36:44 +0300 [thread overview]
Message-ID: <ZOiEPBtPpsygxRiM@skv.local> (raw)
In-Reply-To: <20230824144952.5b908649@slackpad.lan>
Hi Andre,
On 23-08-24 14:50, Andre Przywara wrote:
> On Wed, 23 Aug 2023 21:36:51 +0200
> Jernej Škrabec <jernej.skrabec@gmail.com> wrote:
>
>
> Hi Andrey,
>
> > send new revision as standalone e-mail, not as reply to old discussion.
> >
> > Dne torek, 22. avgust 2023 ob 11:23:58 CEST je Andrey Skvortsov napisal(a):
> > > This patch reserves some memory in the DTS and sets up a
> > > pstore device tree node to enable pstore support.
> > >
> > > In general any DRAM address, that isn't overwritten during a boot is
> > > suitable for pstore.
> > >
> > > Range from 0x40000000 - 0x50000000 is heavily used by u-boot for
> > > internal use and to load kernel, fdt, fdto, scripts, pxefile and ramdisk
> > > later in the boot process. Ramdisk start address is 0x4FF00000,
> > > initramfs for kernel with some hacking features and debug info enabled
> > > can take more than 100Mb and final address will be around 0x58000000.
> > > Address 0x61000000 will most likely not overlap with that.
> >
> > There are other bootloaders as U-Boot, especially on PinePhone. Are you sure
> > it works there too? What about U-Boot configuration, will those addresses still
> > be used if configuration is changed?
>
> Also going along with what Pavel said (that's it more a policy
> decision, not a device property), I feel like this node should be added
> by the bootloader then. And indeed U-Boot has support for that already.
> From skimming over the code in cmd/pstore.c: if you enable
> CONFIG_CMD_PSTORE and set CONFIG_CMD_PSTORE_MEM_ADDR to your chosen
> address, then the U-Boot code will insert a reserved memory node on the
> fly. Would that solve your problem?
>
I've tried pstore command in u-boot in the past to make sure it's
working there as well. I didn't know, that it adds reserved-memory
node as well. Thanks, Andre. That is very helpful.
I've tried it again without patching a kernel as you
suggested. Unfortunately it's not working on A64.
If there is no reserved-memory defined, u-boot adds a new one with
following properties:
reserved-memory {
#address-cells = <2>;
#size-cells = <2>;
ranges;
}
But with these default address-cells and size-cells values, pstore
isn't working on A64. Root node for A64 defines 'address-cells' and 'size-cells' as 1.
dtc complains if reserved-memory has different address-cells and
size-cells.
```
Warning (ranges_format): /reserved-memory:ranges: empty "ranges" property but its #address-cells (2) differs from / (1)
```
If empty reserved-memory is added to
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi in the kernel, then
u-boot adds working pstore subnode.
```
reserved-memory {
#address-cells = <1>;
#size-cells = <1>;
ranges;
/* bootloader will add new entries here
* for example, for pstore.
*/
};
```
It looks like a bug in u-boot for me. IMHO, it should look at
#address-cells/#size-cells of the root-node for default values. I have
tried that and this way pstore is working without any changes to the
kernel dts. What do you think? Should I submit fix to u-boot instead?
--
Best regards,
Andrey Skvortsov
_______________________________________________
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:[~2023-08-25 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230724213457.24593-1-andrej.skvortzov@gmail.com>
2023-07-27 14:57 ` [PATCH] arm64: dts: pinephone: Add pstore support for PinePhone A64 Andre Przywara
2023-07-28 20:25 ` Andrey Skvortsov
2023-08-21 16:08 ` Pavel Machek
2023-08-22 9:23 ` [PATCH v2] " Andrey Skvortsov
2023-08-23 19:36 ` Jernej Škrabec
2023-08-24 13:50 ` Andre Przywara
2023-08-25 10:36 ` Andrey Skvortsov [this message]
2023-08-22 9:26 ` [PATCH] " Andrey Skvortsov
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=ZOiEPBtPpsygxRiM@skv.local \
--to=andrej.skvortzov@gmail.com \
--cc=andre.przywara@arm.com \
--cc=arnaud.ferraris@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=jernej.skrabec@gmail.com \
--cc=keescook@chromium.org \
--cc=kernel@undef.tools \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=tony.luck@intel.com \
--cc=wens@csie.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).