From: Alistair Delva <adelva@google.com> To: linux-kernel@vger.kernel.org Cc: Kenny Root <kroot@google.com>, Rob Herring <robh+dt@kernel.org>, devicetree@vger.kernel.org, linux-nvdimm@lists.01.org, kernel-team@android.com Subject: [PATCH 2/2] dt-bindings: pmem-region: Document memory-region Date: Sat, 22 Feb 2020 10:30:10 -0800 [thread overview] Message-ID: <20200222183010.197844-2-adelva@google.com> (raw) In-Reply-To: <20200222183010.197844-1-adelva@google.com> From: Kenny Root <kroot@google.com> Add documentation and example for memory-region in pmem. Signed-off-by: Kenny Root <kroot@google.com> Signed-off-by: Alistair Delva <adelva@google.com> Cc: "Oliver O'Halloran" <oohall@gmail.com> Cc: Rob Herring <robh+dt@kernel.org> Cc: Dan Williams <dan.j.williams@intel.com> Cc: Vishal Verma <vishal.l.verma@intel.com> Cc: Dave Jiang <dave.jiang@intel.com> Cc: Ira Weiny <ira.weiny@intel.com> Cc: devicetree@vger.kernel.org Cc: linux-nvdimm@lists.01.org Cc: kernel-team@android.com --- .../devicetree/bindings/pmem/pmem-region.txt | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/Documentation/devicetree/bindings/pmem/pmem-region.txt b/Documentation/devicetree/bindings/pmem/pmem-region.txt index 5cfa4f016a00..851ffa71967e 100644 --- a/Documentation/devicetree/bindings/pmem/pmem-region.txt +++ b/Documentation/devicetree/bindings/pmem/pmem-region.txt @@ -29,6 +29,18 @@ Required properties: in a separate device node. Having multiple address ranges in a node implies no special relationship between the two ranges. + This property may be replaced or supplemented with a + memory-region property. Only one of reg or memory-region + properties is required. + + - memory-region: + Reference to the reserved memory node. The reserved memory + node should be defined as per the bindings in + reserved-memory.txt + + This property may be replaced or supplemented with a reg + property. Only one of reg or memory-region is required. + Optional properties: - Any relevant NUMA assocativity properties for the target platform. @@ -63,3 +75,21 @@ Examples: volatile; }; + + /* + * This example uses a reserved-memory entry instead of + * specifying the memory region directly in the node. + */ + + reserved-memory { + pmem_1: pmem@5000 { + no-map; + reg = <0x00005000 0x00001000>; + }; + }; + + pmem@1 { + compatible = "pmem-region"; + memory-region = <&pmem_1>; + }; + -- 2.25.0.265.gbab2e86ba0-goog _______________________________________________ Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: Alistair Delva <adelva@google.com> To: linux-kernel@vger.kernel.org Cc: Kenny Root <kroot@google.com>, "Oliver O'Halloran" <oohall@gmail.com>, Rob Herring <robh+dt@kernel.org>, Dan Williams <dan.j.williams@intel.com>, Vishal Verma <vishal.l.verma@intel.com>, Dave Jiang <dave.jiang@intel.com>, Ira Weiny <ira.weiny@intel.com>, devicetree@vger.kernel.org, linux-nvdimm@lists.01.org, kernel-team@android.com Subject: [PATCH 2/2] dt-bindings: pmem-region: Document memory-region Date: Sat, 22 Feb 2020 10:30:10 -0800 [thread overview] Message-ID: <20200222183010.197844-2-adelva@google.com> (raw) In-Reply-To: <20200222183010.197844-1-adelva@google.com> From: Kenny Root <kroot@google.com> Add documentation and example for memory-region in pmem. Signed-off-by: Kenny Root <kroot@google.com> Signed-off-by: Alistair Delva <adelva@google.com> Cc: "Oliver O'Halloran" <oohall@gmail.com> Cc: Rob Herring <robh+dt@kernel.org> Cc: Dan Williams <dan.j.williams@intel.com> Cc: Vishal Verma <vishal.l.verma@intel.com> Cc: Dave Jiang <dave.jiang@intel.com> Cc: Ira Weiny <ira.weiny@intel.com> Cc: devicetree@vger.kernel.org Cc: linux-nvdimm@lists.01.org Cc: kernel-team@android.com --- .../devicetree/bindings/pmem/pmem-region.txt | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/Documentation/devicetree/bindings/pmem/pmem-region.txt b/Documentation/devicetree/bindings/pmem/pmem-region.txt index 5cfa4f016a00..851ffa71967e 100644 --- a/Documentation/devicetree/bindings/pmem/pmem-region.txt +++ b/Documentation/devicetree/bindings/pmem/pmem-region.txt @@ -29,6 +29,18 @@ Required properties: in a separate device node. Having multiple address ranges in a node implies no special relationship between the two ranges. + This property may be replaced or supplemented with a + memory-region property. Only one of reg or memory-region + properties is required. + + - memory-region: + Reference to the reserved memory node. The reserved memory + node should be defined as per the bindings in + reserved-memory.txt + + This property may be replaced or supplemented with a reg + property. Only one of reg or memory-region is required. + Optional properties: - Any relevant NUMA assocativity properties for the target platform. @@ -63,3 +75,21 @@ Examples: volatile; }; + + /* + * This example uses a reserved-memory entry instead of + * specifying the memory region directly in the node. + */ + + reserved-memory { + pmem_1: pmem@5000 { + no-map; + reg = <0x00005000 0x00001000>; + }; + }; + + pmem@1 { + compatible = "pmem-region"; + memory-region = <&pmem_1>; + }; + -- 2.25.0.265.gbab2e86ba0-goog
next prev parent reply other threads:[~2020-02-22 18:30 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-22 18:30 [PATCH 1/2] libnvdimm/of_pmem: handle memory-region in DT Alistair Delva 2020-02-22 18:30 ` Alistair Delva 2020-02-22 18:30 ` Alistair Delva [this message] 2020-02-22 18:30 ` [PATCH 2/2] dt-bindings: pmem-region: Document memory-region Alistair Delva 2020-02-23 14:56 ` [PATCH 1/2] libnvdimm/of_pmem: handle memory-region in DT Ira Weiny 2020-02-23 14:56 ` Ira Weiny 2020-02-24 1:41 ` Oliver O'Halloran 2020-02-24 1:41 ` Oliver O'Halloran 2020-02-24 1:43 ` Alistair Delva 2020-02-24 1:43 ` Alistair Delva 2020-02-24 1:30 ` Oliver O'Halloran 2020-02-24 1:30 ` Oliver O'Halloran
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=20200222183010.197844-2-adelva@google.com \ --to=adelva@google.com \ --cc=devicetree@vger.kernel.org \ --cc=kernel-team@android.com \ --cc=kroot@google.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nvdimm@lists.01.org \ --cc=robh+dt@kernel.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.