summaryrefslogtreecommitdiff
path: root/sound/soc/sirf/Kconfig
blob: 840058dcad096c2d2c5670da962cdb76f1e925ec (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
config SND_SOC_SIRF
	tristate "SoC Audio for the SiRF SoC chips"
	depends on ARCH_SIRF || COMPILE_TEST
	select SND_SOC_GENERIC_DMAENGINE_PCM

config SND_SOC_SIRF_AUDIO
	tristate "SoC Audio support for SiRF internal audio codec"
	depends on SND_SOC_SIRF
	select SND_SOC_SIRF_AUDIO_CODEC
	select SND_SOC_SIRF_AUDIO_PORT

config SND_SOC_SIRF_AUDIO_PORT
	select REGMAP_MMIO
	tristate

config SND_SOC_SIRF_USP
	tristate "SoC Audio (I2S protocol) for SiRF SoC USP interface"
	depends on SND_SOC_SIRF
	select REGMAP_MMIO
	tristate
3cccf21e02bb1fdd3b852547d75c /fs/xfs/xfs_extent_busy.h parent0c744ea4f77d72b3dcebb7a8f2684633ec79be88 (diff)
tracing: Fix hwlat kthread migration
The hwlat tracer creates a kernel thread at start of the tracer. It is pinned to a single CPU and will move to the next CPU after each period of running. If the user modifies the migration thread's affinity, it will not change after that happens. The original code created the thread at the first instance it was called, but later was changed to destroy the thread after the tracer was finished, and would not be created until the next instance of the tracer was established. The code that initialized the affinity was only called on the initial instantiation of the tracer. After that, it was not initialized, and the previous affinity did not match the current newly created one, making it appear that the user modified the thread's affinity when it did not, and the thread failed to migrate again. Cc: stable@vger.kernel.org Fixes: 0330f7aa8ee6 ("tracing: Have hwlat trace migrate across tracing_cpumask CPUs") Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'fs/xfs/xfs_extent_busy.h')