Searched hist:e3654eca70d63704c94a60a2aafc0b3c7b46a00b (Results 1 – 6 of 6) sorted by relevance
/linux/drivers/nvdimm/ |
H A D | core.c | diff e3654eca70d63704c94a60a2aafc0b3c7b46a00b Fri Apr 29 01:17:07 CEST 2016 Dan Williams <dan.j.williams@intel.com> 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>
|
H A D | nd-core.h | diff e3654eca70d63704c94a60a2aafc0b3c7b46a00b Fri Apr 29 01:17:07 CEST 2016 Dan Williams <dan.j.williams@intel.com> 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>
|
H A D | dimm_devs.c | diff e3654eca70d63704c94a60a2aafc0b3c7b46a00b Fri Apr 29 01:17:07 CEST 2016 Dan Williams <dan.j.williams@intel.com> 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>
|
H A D | bus.c | diff e3654eca70d63704c94a60a2aafc0b3c7b46a00b Fri Apr 29 01:17:07 CEST 2016 Dan Williams <dan.j.williams@intel.com> 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>
|
/linux/include/linux/ |
H A D | libnvdimm.h | diff e3654eca70d63704c94a60a2aafc0b3c7b46a00b Fri Apr 29 01:17:07 CEST 2016 Dan Williams <dan.j.williams@intel.com> 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>
|
/linux/tools/testing/nvdimm/test/ |
H A D | nfit.c | diff e3654eca70d63704c94a60a2aafc0b3c7b46a00b Fri Apr 29 01:17:07 CEST 2016 Dan Williams <dan.j.williams@intel.com> 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>
|