android_kernel_xiaomi_sm8350/arch/powerpc/platforms/pseries/Makefile

obj-y			:= pci.o lpar.o hvCall.o nvram.o reconfig.o \
			   setup.o iommu.o ras.o rtasd.o
obj-$(CONFIG_SMP)	+= smp.o
obj-$(CONFIG_IBMVIO)	+= vio.o
obj-$(CONFIG_XICS)	+= xics.o
obj-$(CONFIG_EEH)    += eeh.o eeh_event.o
powerpc: move pSeries files to arch/powerpc/platforms/pseries Signed-off-by: Paul Mackerras <paulus@samba.org> 2005-10-10 08:03:41 -04:00			`obj-y := pci.o lpar.o hvCall.o nvram.o reconfig.o \`
powerpc: Merge remaining RTAS code This moves rtas-proc.c and rtas_flash.c into arch/powerpc/kernel, since cell wants them as well as pseries (and chrp can use rtas-proc.c too, at least in principle). rtas_fw.c is gone, with its bits moved into rtas_flash.c and rtas.c. Signed-off-by: Paul Mackerras <paulus@samba.org> 2005-11-02 22:41:19 -05:00			`setup.o iommu.o ras.o rtasd.o`
powerpc: move pSeries files to arch/powerpc/platforms/pseries Signed-off-by: Paul Mackerras <paulus@samba.org> 2005-10-10 08:03:41 -04:00			`obj-$(CONFIG_SMP) += smp.o`
			`obj-$(CONFIG_IBMVIO) += vio.o`
[PATCH] powerpc: Move xics.[ch] into platforms/pseries This patch moves the XICS interrupt controller code into the platforms/pseries directory, since it only appears on pSeries machines. If it ever appears on some other machine we can move it to sysdev, although xics.c itself will need a bunch of changes in that case to remove pSeries specific assumptions. Signed-off-by: David Gibson <dwg@au1.ibm.com> Signed-off-by: Paul Mackerras <paulus@samba.org> 2005-10-28 01:35:50 -04:00			`obj-$(CONFIG_XICS) += xics.o`
[PATCH] ppc64: PCI error event dispatcher 12-eeh-event-dispatcher.patch ppc64: EEH Recovery dispatcher thread This patch adds a mechanism to create recovery threads when an EEH event is received. Since an EEH freeze state may be detected within an interrupt context, we need to get out of the interrupt context before starting recovery. This dispatcher does this in two steps: first, it uses a workqueue to get out, and then lanuches a kernel thread, so that the recovery routine can sleep for exteded periods without upseting the keventd. A kernel thread is created with each EEH event, rather than having one long-running daemon started at boot time. This is because it is anticipated that EEH events will be very rare (very very rare, ideally) and so its pointless to cluter the process tables with a daemon that will almost never run. Signed-off-by: Linas Vepstas <linas@austin.ibm.com> Signed-off-by: Paul Mackerras <paulus@samba.org> 2005-11-03 19:50:04 -05:00			`obj-$(CONFIG_EEH) += eeh.o eeh_event.o`