Eugeniy Paltsev 3624379d90 ARC: IOC: panic if kernel was started with previously enabled IOC ... If IOC was already enabled (due to bootloader) it technically needs to be reconfigured with aperture base,size corresponding to Linux memory map which will certainly be different than uboot's. But disabling and reenabling IOC when DMA might be potentially active is tricky business. To avoid random memory issues later, just panic here and ask user to upgrade bootloader to one which doesn't enable IOC This was actually seen as issue on some of the HSDK board with a version of uboot which enabled IOC. There were random issues later with starting of X or peripherals etc. Also while I'm at it, replace hardcoded bits in ARC_REG_IO_COH_PARTIAL and ARC_REG_IO_COH_ENABLE registers by definitions. Inspired by: https://lkml.org/lkml/2018/1/19/557 Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com> Signed-off-by: Vineet Gupta <vgupta@synopsys.com>		2018-11-12 10:38:27 -08:00
..
asm	ARC: IOC: panic if kernel was started with previously enabled IOC	2018-11-12 10:38:27 -08:00
uapi/asm	y2038: Remove stat64 family from default syscall set	2018-08-29 15:42:20 +02:00