diff options
author | Dan Williams <dan.j.williams@intel.com> | 2015-05-31 14:41:48 -0400 |
---|---|---|
committer | Dan Williams <dan.j.williams@intel.com> | 2015-06-24 21:24:10 -0400 |
commit | 4d88a97aa9e8cfa6460aab119c5da60ad2267423 (patch) | |
tree | f96989f3240720c647a48dd493d895b58b052b10 /include/linux/hpet.h | |
parent | 62232e45f4a265abb43f0acf16e58f5d0b6e1ec9 (diff) | |
download | linux-4d88a97aa9e8cfa6460aab119c5da60ad2267423.tar.gz linux-4d88a97aa9e8cfa6460aab119c5da60ad2267423.tar.bz2 linux-4d88a97aa9e8cfa6460aab119c5da60ad2267423.zip |
libnvdimm, nvdimm: dimm driver and base libnvdimm device-driver infrastructure
* Implement the device-model infrastructure for loading modules and
attaching drivers to nvdimm devices. This is a simple association of a
nd-device-type number with a driver that has a bitmask of supported
device types. To facilitate userspace bind/unbind operations 'modalias'
and 'devtype', that also appear in the uevent, are added as generic
sysfs attributes for all nvdimm devices. The reason for the device-type
number is to support sub-types within a given parent devtype, be it a
vendor-specific sub-type or otherwise.
* The first consumer of this infrastructure is the driver
for dimm devices. It simply uses control messages to retrieve and
store the configuration-data image (label set) from each dimm.
Note: nd_device_register() arranges for asynchronous registration of
nvdimm bus devices by default.
Cc: Greg KH <gregkh@linuxfoundation.org>
Cc: Neil Brown <neilb@suse.de>
Acked-by: Christoph Hellwig <hch@lst.de>
Tested-by: Toshi Kani <toshi.kani@hp.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'include/linux/hpet.h')
0 files changed, 0 insertions, 0 deletions