[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_Jsq+EV02YBqEGoJrsJW8Y+g_GkB_LkTwWCxNCb3F+8MSdyw@mail.gmail.com>
Date: Thu, 21 May 2020 07:29:17 -0600
From: Rob Herring <robh+dt@...nel.org>
To: Chen Zhou <chenzhou10@...wei.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>, dyoung@...hat.com,
Baoquan He <bhe@...hat.com>, Arnd Bergmann <arnd@...db.de>,
John.p.donnelly@...cle.com, pkushwaha@...vell.com,
Simon Horman <horms@...ge.net.au>,
Hanjun Guo <guohanjun@...wei.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>, devicetree@...r.kernel.org,
Linux Doc Mailing List <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
kexec@...ts.infradead.org
Subject: Re: [PATCH v8 5/5] dt-bindings: chosen: Document linux,low-memory-range
for arm64 kdump
On Thu, May 21, 2020 at 3:35 AM Chen Zhou <chenzhou10@...wei.com> wrote:
>
> Add documentation for DT property used by arm64 kdump:
> linux,low-memory-range.
> "linux,low-memory-range" is an another memory region used for crash
> dump kernel devices.
>
> Signed-off-by: Chen Zhou <chenzhou10@...wei.com>
> ---
> Documentation/devicetree/bindings/chosen.txt | 25 ++++++++++++++++++++
> 1 file changed, 25 insertions(+)
chosen is now a schema documented here[1].
> diff --git a/Documentation/devicetree/bindings/chosen.txt b/Documentation/devicetree/bindings/chosen.txt
> index 45e79172a646..bfe6fb6976e6 100644
> --- a/Documentation/devicetree/bindings/chosen.txt
> +++ b/Documentation/devicetree/bindings/chosen.txt
> @@ -103,6 +103,31 @@ While this property does not represent a real hardware, the address
> and the size are expressed in #address-cells and #size-cells,
> respectively, of the root node.
>
> +linux,low-memory-range
> +----------------------
> +This property (arm64 only) holds a base address and size, describing a
> +limited region below 4G. Similar to "linux,usable-memory-range", it is
> +an another memory range which may be considered available for use by the
> +kernel.
Why can't you just add a range to "linux,usable-memory-range"? It
shouldn't be hard to figure out which part is below 4G.
Rob
[1] https://github.com/devicetree-org/dt-schema/blob/master/schemas/chosen.yaml
Powered by blists - more mailing lists