devicetree-spec.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] Add 'hotpluggable' property for /memory nodes
Date: Wed,  4 Mar 2020 18:36:27 -0600	[thread overview]
Message-ID: <20200305003627.3994-1-robh@kernel.org> (raw)

The 'hotpluggable' property has been documented and supported in the Linux
kernel since 2016. Add the property to the spec so we can remove the kernel
specific documentation.

Signed-off-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
---
 source/devicenodes.rst | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/source/devicenodes.rst b/source/devicenodes.rst
index 519aa3776884..3aa4650f6a59 100644
--- a/source/devicenodes.rst
+++ b/source/devicenodes.rst
@@ -151,6 +151,9 @@ If the VLE storage attribute is supported, with VLE=0.
                                                            address, size). The effective and physical
                                                            address shall each be 64-bit (``<u64>`` value),
                                                            and the size shall be 32-bits (``<u32>`` value).
+   ``hotpluggable``        O      ``<empty>``              Specifies an explicit hint to the operating
+                                                           system that this memory may potentially be
+                                                           removed later.
    Usage legend: R=Required, O=Optional, OR=Optional but Recommended, SD=See Definition
    =======================================================================================================
 
@@ -738,4 +741,3 @@ each with their own on-chip L2 and a shared L3.
             };
         };
     };
-
-- 
2.20.1


                 reply	other threads:[~2020-03-05  0:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200305003627.3994-1-robh@kernel.org \
    --to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).