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: <[email protected]> > Cc: Lv Zheng <[email protected]> > Cc: Robert Moore <[email protected]> > Cc: Rafael J. Wysocki <[email protected]> > Acked-by: Jeff Moyer <[email protected]> > Signed-off-by: Dan Williams <[email protected]>
Acked-by: Rafael J. Wysocki <[email protected]> [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, > + }, > +}; > + -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
