nfit, libnvdimm: clarify "commands" vs "_DSMs"
authorDan Williams <dan.j.williams@intel.com>
Thu, 28 Apr 2016 23:17:07 +0000 (16:17 -0700)
committerDan Williams <dan.j.williams@intel.com>
Thu, 28 Apr 2016 23:23:16 +0000 (16:23 -0700)
commite3654eca70d63704c94a60a2aafc0b3c7b46a00b
tree2e2d1c136d04f1918908b841a45de2c551f01533
parent40abf9be8f52d440e442206182916e3dcc68f722
nfit, libnvdimm: clarify "commands" vs "_DSMs"

Clarify the distinction between "commands", the ioctls userspace calls
to request the kernel take some action on a given dimm device, and
"_DSMs", the actual function numbers used in the firmware interface to
the DIMM.  _DSMs are ACPI specific whereas commands are Linux kernel
generic.

This is in preparation for breaking the 1:1 implicit relationship
between the kernel ioctl number space and the firmware specific function
numbers.

Cc: Jerry Hoemann <jerry.hoemann@hpe.com>
Cc: Christoph Hellwig <hch@infradead.org>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
drivers/acpi/nfit.c
drivers/acpi/nfit.h
drivers/nvdimm/bus.c
drivers/nvdimm/core.c
drivers/nvdimm/dimm_devs.c
drivers/nvdimm/nd-core.h
include/linux/libnvdimm.h
tools/testing/nvdimm/test/nfit.c