summaryrefslogtreecommitdiffstats
path: root/arch/m68k/bvme6000
diff options
context:
space:
mode:
authorCédric Le Goater <clg@fr.ibm.com>2015-04-08 19:19:50 +0200
committerGuenter Roeck <linux@roeck-us.net>2015-04-08 10:34:20 -0700
commit3df2f59f0aae2f5380a9d8037c91dcab75c4478d (patch)
tree8e49b6332b95a8fa5847185ff39e855fc2b25382 /arch/m68k/bvme6000
parent2bcd3787b946b725a37763c0877da0996f5ec064 (diff)
downloadlinux-3df2f59f0aae2f5380a9d8037c91dcab75c4478d.tar.gz
linux-3df2f59f0aae2f5380a9d8037c91dcab75c4478d.tar.bz2
linux-3df2f59f0aae2f5380a9d8037c91dcab75c4478d.zip
hwmon: (ibmpowernv) pretty print labels
The new OPAL device tree adds a few properties which can be used to add extra information on the sensor label. In the case of a cpu core sensor, the firmware exposes the physical identifier of the core in the "ibm,pir" property. The driver translates this identifier in a linux cpu number and prints out a range corresponding to the hardware threads of the core (as they share the same sensor). The numbering gives a hint on the localization of the core in the system (which socket, which chip). Signed-off-by: Cédric Le Goater <clg@fr.ibm.com> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Diffstat (limited to 'arch/m68k/bvme6000')
0 files changed, 0 insertions, 0 deletions