diff options
| author | Michael Ellerman <mpe@ellerman.id.au> | 2017-08-22 07:14:50 +0200 |
|---|---|---|
| committer | Michael Ellerman <mpe@ellerman.id.au> | 2017-08-23 14:27:03 +0200 |
| commit | bcf21e3a97a1247178338793df9ae332a036e22b (patch) | |
| tree | 2884cc03dd8aac627c77683ca232b850f86faaf6 /arch/powerpc/sysdev/axonram.c | |
| parent | Merge branch 'fixes' into next (diff) | |
| download | linux-bcf21e3a97a1247178338793df9ae332a036e22b.tar.xz linux-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 'arch/powerpc/sysdev/axonram.c')
0 files changed, 0 insertions, 0 deletions