powerpc/powernv: Move SCOM access code into powernv platform
authorAndrew Donnellan <ajd@linux.ibm.com>
Thu, 9 May 2019 05:11:15 +0000 (15:11 +1000)
committerMichael Ellerman <mpe@ellerman.id.au>
Mon, 5 Aug 2019 08:53:03 +0000 (18:53 +1000)
commit08a456aa643776757e07adfdebe7f7681117d144
treeae477a0ad078276e74c99e5ee02b82b5bbeb56de
parent0df3e42167caaf9f8c7b64de3da40a459979afe8
powerpc/powernv: Move SCOM access code into powernv platform

The powernv platform is the only one that directly accesses SCOMs.
Move the support code to platforms/powernv, and get rid of the
PPC_SCOM Kconfig option, as SCOM support is always selected when
compiling for powernv.

This also means that the Kconfig item for CONFIG_SCOM_DEBUGFS will
show up in menuconfig in the platform menu, rather than at the root,
which is a much better location.

Signed-off-by: Andrew Donnellan <ajd@linux.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20190509051119.7694-1-ajd@linux.ibm.com
arch/powerpc/include/asm/scom.h [deleted file]
arch/powerpc/platforms/powernv/Kconfig
arch/powerpc/platforms/powernv/Makefile
arch/powerpc/platforms/powernv/opal-xscom.c
arch/powerpc/platforms/powernv/scom.c [new file with mode: 0644]
arch/powerpc/platforms/powernv/scom.h [new file with mode: 0644]
arch/powerpc/sysdev/Kconfig
arch/powerpc/sysdev/Makefile
arch/powerpc/sysdev/scom.c [deleted file]