blob: af0894f2a0953ce5eaf07d2c7c8d7e746ff50f3a (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
#
# Generic framework for controlling remote processors
#
# Remote proc gets selected by whoever wants it.
config REMOTE_PROC
tristate
config REMOTE_PROC_AUTOSUSPEND
bool "Autosuspend support for remoteproc"
depends on REMOTE_PROC
default y
help
Say Y here if you want remote processor to suspend
after some time of inactivity.
# can't be tristate, due to omap_device_* and omap_hwmod_* dependency
config OMAP_REMOTE_PROC
bool "OMAP remoteproc support"
depends on ARCH_OMAP4
select OMAP_IOMMU
select REMOTE_PROC
default y
help
Say y here to support OMAP's remote processors (dual M3
and DSP on OMAP4) via the remote processor framework.
Currently only supported on OMAP4.
Usually you want to say y here, in order to enable multimedia
use-cases to run on your platform (multimedia codecs are
offloaded to remote DSP processors using this framework).
It's safe to say n here if you're not interested in multimedia
offloading or just want a bare minium kernel.
config OMAP_RPRES
bool "Remote Processor Resources"
depends on OMAP_REMOTE_PROC
default y
help
Say Y here if you want to use OMAP remote processor resources
frame work.
config REMOTEPROC_WATCHDOG
bool "OMAP remoteproc watchdog timer"
depends on REMOTE_PROC
default y
help
Say y to enable watchdog timer for remote cores
config REMOTEPROC_CORE_DUMP
bool "Support for extracting a core dump from a remote processor"
depends on REMOTE_PROC
default y
help
Say y to enable extracting a core dump from a running remote
processor at <debugfs>/remoteproc/<remoteproc>/core. Extracting the
core dump does not pause the remote processor--this must be
implemented separately.
|
