summaryrefslogtreecommitdiff
path: root/drivers/leds/leds-fsg.c
diff options
context:
space:
mode:
authorShanker Donthineni <shankerd@codeaurora.org>2017-03-29 06:39:19 -0500
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2017-04-18 16:56:39 +0200
commit79f97c3051e16b117b47e0586a368c4f54a82909 (patch)
tree56964eb425a1fdac7dff8c2f6da4fab050cd8b49 /drivers/leds/leds-fsg.c
parent4f7d029b9bf009fbee76bb10c0c4351a1870d2f3 (diff)
ACPI / platform: Update platform device NUMA node based on _PXM method
The optional _PXM method evaluates to an integer that identifies the proximity domain of a device object. On ACPI based kernel boot, the field numa_node in 'struct device' is always set to -1 irrespective of _PXM value that is specified in the ACPI device object. But in case of device-tree based kernel boot the numa_node field is populated and reflects to a DT property that is specified in DTS according to the below document. https://www.kernel.org/doc/Documentation/devicetree/bindings/numa.txt http://lxr.free-electrons.com/source/drivers/of/device.c#L54 Without this patch dev_to_node() always returns -1 for all platform devices. This patch adds support for the ACPI _PXM method and updates the platform device NUMA node id using acpi_get_node() which provides the PXM-to-NUMA mapping information. The individual platform device drivers should be able to use the NUMA-aware memory allocation functions kmalloc_node() and alloc_pages_node() to improve performance. Signed-off-by: Shanker Donthineni <shankerd@codeaurora.org> Reviewed-by: Hanjun Guo <hanjun.guo@linaro.org> Tested-by: Jiandi An <anjiandi@codeaurora.org> [ rjw: Subject / changelog ] Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/leds/leds-fsg.c')
0 files changed, 0 insertions, 0 deletions