From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Williams Subject: Re: [RESEND v2 3/4] doc/devicetree: Persistent memory region bindings Date: Tue, 3 Apr 2018 10:37:51 -0700 Message-ID: References: <20180403142415.30083-1-oohall@gmail.com> <20180403142415.30083-3-oohall@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20180403142415.30083-3-oohall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-nvdimm-bounces-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org Sender: "Linux-nvdimm" To: Oliver O'Halloran Cc: Device Tree , linuxppc-dev , linux-nvdimm List-Id: devicetree@vger.kernel.org On Tue, Apr 3, 2018 at 7:24 AM, Oliver O'Halloran wrote: > Add device-tree binding documentation for the nvdimm region driver. > > Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org > Signed-off-by: Oliver O'Halloran > --- > v2: Changed name from nvdimm-region to pmem-region. > Cleaned up the example binding and fixed the overlapping regions. > Added support for multiple regions in a single reg. > --- > .../devicetree/bindings/pmem/pmem-region.txt | 80 ++++++++++++++++++++++ > MAINTAINERS | 1 + > 2 files changed, 81 insertions(+) > create mode 100644 Documentation/devicetree/bindings/pmem/pmem-region.txt Device-tree folks, does this look, ok? Oliver, is there any concept of a management interface to the device(s) backing these regions? libnvdimm calls these "nmem" devices and support operations like health status and namespace label management.