Re: [PATCH v2 1/5] powerpc/powernv: Move SCOM access code into powernv platform

2019-08-10 Thread Michael Ellerman
On Thu, 2019-05-09 at 05:11:15 UTC, Andrew Donnellan wrote: > 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

Re: [PATCH v2 1/5] powerpc/powernv: Move SCOM access code into powernv platform

2019-07-31 Thread Michael Ellerman
Andrew Donnellan writes: > On 9/5/19 3:11 pm, Andrew Donnellan wrote: >> 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. >

Re: [PATCH v2 1/5] powerpc/powernv: Move SCOM access code into powernv platform

2019-06-03 Thread Andrew Donnellan
On 9/5/19 3:11 pm, Andrew Donnellan wrote: 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 it

[PATCH v2 1/5] powerpc/powernv: Move SCOM access code into powernv platform

2019-05-08 Thread Andrew Donnellan
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 actually show