From: "Rafael J. Wysocki" <rjw@rjwysocki.net> To: Dan Williams <dan.j.williams@intel.com> Cc: linux-nvdimm@lists.01.org, mingo@kernel.org, sfr@canb.auug.org.au, rafael@kernel.org, neilb@suse.de, gregkh@linuxfoundation.org, "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>, linux-kernel@vger.kernel.org, Robert Moore <robert.moore@intel.com>, linux-acpi@vger.kernel.org, jmoyer@redhat.com, Lv Zheng <lv.zheng@intel.com>, linux-api@vger.kernel.org, akpm@linux-foundation.org, axboe@kernel.dk, hch@lst.de Subject: Re: [PATCH v6 02/21] libnvdimm, nfit: initial libnvdimm infrastructure and NFIT support Date: Wed, 17 Jun 2015 23:59:29 +0200 [thread overview] Message-ID: <1863642.qegEO3HtMW@vostro.rjw.lan> (raw) In-Reply-To: <20150611201018.25175.78715.stgit@dwillia2-desk3.amr.corp.intel.com> On Thursday, June 11, 2015 04:10:18 PM Dan Williams wrote: > A struct nvdimm_bus is the anchor device for registering nvdimm > resources and interfaces, for example, a character control device, > nvdimm devices, and I/O region devices. The ACPI NFIT (NVDIMM Firmware > Interface Table) is one possible platform description for such > non-volatile memory resources in a system. The nfit.ko driver attaches > to the "ACPI0012" device that indicates the presence of the NFIT and > parses the table to register a struct nvdimm_bus instance. > > Cc: <linux-acpi@vger.kernel.org> > Cc: Lv Zheng <lv.zheng@intel.com> > Cc: Robert Moore <robert.moore@intel.com> > Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com> > Acked-by: Jeff Moyer <jmoyer@redhat.com> > Signed-off-by: Dan Williams <dan.j.williams@intel.com> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> [cut] > + > +static struct acpi_driver acpi_nfit_driver = { > + .name = KBUILD_MODNAME, > + .ids = acpi_nfit_ids, > + .flags = ACPI_DRIVER_ALL_NOTIFY_EVENTS, But this flag is not needed for now IMO. > + .ops = { > + .add = acpi_nfit_add, > + .remove = acpi_nfit_remove, > + }, > +}; > +
WARNING: multiple messages have this Message-ID (diff)
From: "Rafael J. Wysocki" <rjw@rjwysocki.net> To: Dan Williams <dan.j.williams@intel.com> Cc: linux-nvdimm@ml01.01.org, mingo@kernel.org, sfr@canb.auug.org.au, rafael@kernel.org, neilb@suse.de, gregkh@linuxfoundation.org, "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>, linux-kernel@vger.kernel.org, Robert Moore <robert.moore@intel.com>, linux-acpi@vger.kernel.org, jmoyer@redhat.com, Lv Zheng <lv.zheng@intel.com>, linux-api@vger.kernel.org, akpm@linux-foundation.org, axboe@kernel.dk, hch@lst.de Subject: Re: [PATCH v6 02/21] libnvdimm, nfit: initial libnvdimm infrastructure and NFIT support Date: Wed, 17 Jun 2015 23:59:29 +0200 [thread overview] Message-ID: <1863642.qegEO3HtMW@vostro.rjw.lan> (raw) In-Reply-To: <20150611201018.25175.78715.stgit@dwillia2-desk3.amr.corp.intel.com> On Thursday, June 11, 2015 04:10:18 PM Dan Williams wrote: > A struct nvdimm_bus is the anchor device for registering nvdimm > resources and interfaces, for example, a character control device, > nvdimm devices, and I/O region devices. The ACPI NFIT (NVDIMM Firmware > Interface Table) is one possible platform description for such > non-volatile memory resources in a system. The nfit.ko driver attaches > to the "ACPI0012" device that indicates the presence of the NFIT and > parses the table to register a struct nvdimm_bus instance. > > Cc: <linux-acpi@vger.kernel.org> > Cc: Lv Zheng <lv.zheng@intel.com> > Cc: Robert Moore <robert.moore@intel.com> > Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com> > Acked-by: Jeff Moyer <jmoyer@redhat.com> > Signed-off-by: Dan Williams <dan.j.williams@intel.com> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> [cut] > + > +static struct acpi_driver acpi_nfit_driver = { > + .name = KBUILD_MODNAME, > + .ids = acpi_nfit_ids, > + .flags = ACPI_DRIVER_ALL_NOTIFY_EVENTS, But this flag is not needed for now IMO. > + .ops = { > + .add = acpi_nfit_add, > + .remove = acpi_nfit_remove, > + }, > +}; > +
next prev parent reply other threads:[~2015-06-17 21:59 UTC|newest] Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-11 20:09 [PATCH v6 00/21] libnvdimm: non-volatile memory devices Dan Williams 2015-06-11 20:09 ` Dan Williams 2015-06-11 20:10 ` [PATCH v6 01/21] e820, efi: add ACPI 6.0 persistent memory types Dan Williams 2015-06-11 20:10 ` Dan Williams 2015-06-11 20:10 ` Dan Williams 2015-06-11 20:10 ` [PATCH v6 02/21] libnvdimm, nfit: initial libnvdimm infrastructure and NFIT support Dan Williams 2015-06-11 20:10 ` Dan Williams 2015-06-11 20:10 ` Dan Williams 2015-06-17 21:59 ` Rafael J. Wysocki [this message] 2015-06-17 21:59 ` Rafael J. Wysocki 2015-06-17 21:35 ` Dan Williams 2015-06-17 21:35 ` Dan Williams 2015-06-17 21:35 ` Dan Williams 2015-06-11 20:10 ` [PATCH v6 03/21] libnvdimm: control character device and nvdimm_bus sysfs attributes Dan Williams 2015-06-11 20:10 ` Dan Williams 2015-06-11 20:10 ` Dan Williams 2015-06-17 22:00 ` Rafael J. Wysocki 2015-06-17 22:00 ` Rafael J. Wysocki 2015-06-17 22:00 ` Rafael J. Wysocki 2015-06-11 20:10 ` [PATCH v6 04/21] libnvdimm, nfit: dimm/memory-devices Dan Williams 2015-06-11 20:10 ` Dan Williams 2015-06-17 22:02 ` Rafael J. Wysocki 2015-06-17 22:02 ` Rafael J. Wysocki 2015-06-11 20:10 ` [PATCH v6 05/21] libnvdimm: control (ioctl) messages for nvdimm_bus and nvdimm devices Dan Williams 2015-06-11 20:10 ` Dan Williams 2015-06-11 20:10 ` [PATCH v6 06/21] libnvdimm, nvdimm: dimm driver and base libnvdimm device-driver infrastructure Dan Williams 2015-06-11 20:10 ` Dan Williams 2015-06-11 20:10 ` [PATCH v6 07/21] libnvdimm, nfit: regions (block-data-window, persistent memory, volatile memory) Dan Williams 2015-06-11 20:10 ` Dan Williams 2015-06-11 20:10 ` Dan Williams 2015-06-17 22:03 ` Rafael J. Wysocki 2015-06-17 22:03 ` Rafael J. Wysocki 2015-06-11 20:10 ` [PATCH v6 08/21] libnvdimm: support for legacy (non-aliasing) nvdimms Dan Williams 2015-06-11 20:10 ` Dan Williams 2015-06-11 20:10 ` [PATCH v6 09/21] libnvdimm, pmem: move pmem to drivers/nvdimm/ Dan Williams 2015-06-11 20:10 ` Dan Williams 2015-06-11 20:10 ` Dan Williams 2015-06-11 20:11 ` [PATCH v6 10/21] libnvdimm, pmem: add libnvdimm support to the pmem driver Dan Williams 2015-06-11 20:11 ` Dan Williams 2015-06-11 20:11 ` [PATCH v6 11/21] libnvdimm, nfit: add interleave-set state-tracking infrastructure Dan Williams 2015-06-11 20:11 ` Dan Williams 2015-06-11 20:11 ` Dan Williams 2015-06-17 22:06 ` Rafael J. Wysocki 2015-06-17 22:06 ` Rafael J. Wysocki 2015-06-11 20:11 ` [PATCH v6 12/21] libnvdimm: namespace indices: read and validate Dan Williams 2015-06-11 20:11 ` Dan Williams 2015-06-11 20:11 ` [PATCH v6 13/21] libnvdimm: pmem label sets and namespace instantiation Dan Williams 2015-06-11 20:11 ` Dan Williams 2015-06-11 20:11 ` [PATCH v6 14/21] libnvdimm: blk labels " Dan Williams 2015-06-11 20:11 ` Dan Williams 2015-06-11 20:11 ` [PATCH v6 15/21] libnvdimm: write pmem label set Dan Williams 2015-06-11 20:11 ` Dan Williams 2015-06-11 20:11 ` [PATCH v6 16/21] libnvdimm: write blk " Dan Williams 2015-06-11 20:11 ` Dan Williams 2015-06-11 20:11 ` [PATCH v6 17/21] libnvdimm: infrastructure for btt devices Dan Williams 2015-06-11 20:11 ` Dan Williams 2015-06-17 10:49 ` Christoph Hellwig 2015-06-17 10:49 ` Christoph Hellwig 2015-06-17 10:49 ` Christoph Hellwig 2015-06-11 20:11 ` [PATCH v6 18/21] nd_btt: atomic sector updates Dan Williams 2015-06-11 20:11 ` Dan Williams 2015-06-11 20:22 ` Dan Williams 2015-06-11 20:22 ` Dan Williams 2015-06-11 20:11 ` [PATCH v6 19/21] libnvdimm, nfit, nd_blk: driver for BLK-mode access persistent memory Dan Williams 2015-06-11 20:11 ` Dan Williams 2015-06-17 22:09 ` Rafael J. Wysocki 2015-06-17 22:09 ` Rafael J. Wysocki 2015-06-17 22:09 ` Rafael J. Wysocki 2015-06-11 20:11 ` [PATCH v6 20/21] tools/testing/nvdimm: libnvdimm unit test infrastructure Dan Williams 2015-06-11 20:11 ` Dan Williams 2015-06-11 20:12 ` [PATCH v6 21/21] libnvdimm: Non-Volatile Devices Dan Williams 2015-06-11 20:12 ` Dan Williams 2015-06-17 11:26 ` [PATCH v6 00/21] libnvdimm: non-volatile memory devices Christoph Hellwig 2015-06-17 11:26 ` Christoph Hellwig 2015-06-17 11:26 ` Christoph Hellwig 2015-06-17 17:28 ` Dan Williams 2015-06-17 17:28 ` Dan Williams 2015-06-17 17:28 ` Dan Williams
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=1863642.qegEO3HtMW@vostro.rjw.lan \ --to=rjw@rjwysocki.net \ --cc=akpm@linux-foundation.org \ --cc=axboe@kernel.dk \ --cc=dan.j.williams@intel.com \ --cc=gregkh@linuxfoundation.org \ --cc=hch@lst.de \ --cc=jmoyer@redhat.com \ --cc=linux-acpi@vger.kernel.org \ --cc=linux-api@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nvdimm@lists.01.org \ --cc=lv.zheng@intel.com \ --cc=mingo@kernel.org \ --cc=neilb@suse.de \ --cc=rafael.j.wysocki@intel.com \ --cc=rafael@kernel.org \ --cc=robert.moore@intel.com \ --cc=sfr@canb.auug.org.au \ /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.