mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-11-26 20:20:53 +07:00
ba50ea7eb9
The secure sram context save uses dma channels 0 and 1. In order to avoid collision between kernel DMA transfers and ROM code dma transfers, we need to reserve DMA channels 0 1 on high security devices. A bug in ROM code leaves dma irq status bits uncleared. Hence those irq status bits need to be cleared when restoring DMA context after off mode. There was also a faulty parameter given to PPA in the secure ram context save assembly code, which caused interrupts to be enabled during secure ram context save. This caused the save to fail sometimes, which resulted the saved context to be corrupted, but also left DMA channels in secure mode. The secure mode DMA channels caused "DMA secure error with device 0" errors to be displayed. Signed-off-by: Kalle Jokiniemi <kalle.jokiniemi@digia.com> Signed-off-by: Jouni Hogander <jouni.hogander@nokia.com> Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com> |
||
---|---|---|
.. | ||
include/plat | ||
clock.c | ||
common.c | ||
cpu-omap.c | ||
debug-devices.c | ||
debug-leds.c | ||
devices.c | ||
dma.c | ||
dmtimer.c | ||
fb.c | ||
gpio.c | ||
i2c.c | ||
io.c | ||
iommu-debug.c | ||
iommu.c | ||
iopgtable.h | ||
iovmm.c | ||
Kconfig | ||
mailbox.c | ||
Makefile | ||
mcbsp.c | ||
mux.c | ||
ocpi.c | ||
omap_device.c | ||
omap-pm-noop.c | ||
sram.c | ||
usb.c |