summaryrefslogtreecommitdiff
path: root/sound/soc/sti/Kconfig
blob: 64a690077023a44293c89722b75b07ec528e540b (plain)
1
2
3
4
5
6
7
8
9
10
11
#
# STM SoC audio configuration
#
menuconfig SND_SOC_STI
	tristate "SoC Audio support for STI System-On-Chip"
	depends on SND_SOC
	depends on ARCH_STI || COMPILE_TEST
	select SND_SOC_GENERIC_DMAENGINE_PCM
	help
		Say Y if you want to enable ASoC-support for
		any of the STI platforms (e.g. STIH416).
> commit54791b276b4000b307339f269d3bf7db877d536f (patch) tree1c2616bd373ce5ea28aac2a53e32f5b5834901ce /net/decnet/dn_rules.c parent5d0e7705774dd412a465896d08d59a81a345c1e4 (diff)parent047487241ff59374fded8c477f21453681f5995c (diff)
Merge branch 'sparc64-non-resumable-user-error-recovery'
Liam R. Howlett says: ==================== sparc64: Recover from userspace non-resumable PIO & MEM errors A non-resumable error from userspace is able to cause a kernel panic or trap loop due to the setup and handling of the queued traps once in the kernel. This patch series addresses both of these issues. The queues are fixed by simply zeroing the memory before use. PIO errors from userspace will result in a SIGBUS being sent to the user process. The MEM errors form userspace will result in a SIGKILL and also cause the offending pages to be claimed so they are no longer used in future tasks. SIGKILL is used to ensure that the process does not try to coredump and result in an attempt to read the memory again from within kernel space. Although there is a HV call to scrub the memory (mem_scrub), there is no easy way to guarantee that the real memory address(es) are not used by other tasks. Clearing the error with mem_scrub would zero the memory and cause the other processes to proceed with bad data. The handling of other non-resumable errors remain unchanged and will cause a panic. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/decnet/dn_rules.c')