diff options
author | Michael Ellerman <mpe@ellerman.id.au> | 2017-08-22 15:14:50 +1000 |
---|---|---|
committer | Michael Ellerman <mpe@ellerman.id.au> | 2017-08-23 22:27:03 +1000 |
commit | bcf21e3a97a1247178338793df9ae332a036e22b (patch) | |
tree | 2884cc03dd8aac627c77683ca232b850f86faaf6 /drivers/acpi/acpica/tbxfroot.c | |
parent | 15c659ff9d5b367c886166a9854a89b72c524a68 (diff) | |
download | linux-stable-bcf21e3a97a1247178338793df9ae332a036e22b.tar.gz linux-stable-bcf21e3a97a1247178338793df9ae332a036e22b.tar.bz2 linux-stable-bcf21e3a97a1247178338793df9ae332a036e22b.zip |
powerpc/vio: Use device_type to detect family
Currently in the vio.c code we use a comparision against the parent
device node's full path to decide if the device is a PFO or VIO family
device.
Both the ibm,platform-facilities and vdevice nodes are defined by PAPR,
and must have a matching device_type. So instead of using the path we
can instead compare the device_type.
I've checked Qemu and kvmtool both do this correctly, and all the
PowerVM systems I have access to do also. So it seems to be safe.
This removes the dependency on full_name, which is being removed
upstream.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'drivers/acpi/acpica/tbxfroot.c')
0 files changed, 0 insertions, 0 deletions