2010-06-24 07:40:07 -06:00
|
|
|
#
|
|
|
|
# DSP Bridge Driver Support
|
|
|
|
#
|
|
|
|
|
|
|
|
menuconfig TIDSPBRIDGE
|
|
|
|
tristate "DSP Bridge driver"
|
|
|
|
depends on ARCH_OMAP3
|
|
|
|
select OMAP_MBOX_FWK
|
|
|
|
help
|
|
|
|
DSP/BIOS Bridge is designed for platforms that contain a GPP and
|
|
|
|
one or more attached DSPs. The GPP is considered the master or
|
|
|
|
"host" processor, and the attached DSPs are processing resources
|
|
|
|
that can be utilized by applications and drivers running on the GPP.
|
|
|
|
|
|
|
|
This driver depends on OMAP Mailbox (OMAP_MBOX_FWK).
|
|
|
|
|
2010-07-04 07:36:23 -06:00
|
|
|
config TIDSPBRIDGE_DVFS
|
2010-06-24 07:40:07 -06:00
|
|
|
bool "Enable Bridge Dynamic Voltage and Frequency Scaling (DVFS)"
|
|
|
|
depends on TIDSPBRIDGE && OMAP_PM_SRF && CPU_FREQ
|
|
|
|
help
|
|
|
|
DVFS allows DSP Bridge to initiate the operating point change to
|
|
|
|
scale the chip voltage and frequency in order to match the
|
|
|
|
performance and power consumption to the current processing
|
|
|
|
requirements.
|
|
|
|
|
2010-07-04 07:36:23 -06:00
|
|
|
config TIDSPBRIDGE_MEMPOOL_SIZE
|
2010-06-24 07:40:07 -06:00
|
|
|
hex "Physical memory pool size (Byte)"
|
|
|
|
depends on TIDSPBRIDGE
|
|
|
|
default 0x600000
|
|
|
|
help
|
|
|
|
Allocate specified size of memory at booting time to avoid allocation
|
|
|
|
failure under heavy memory fragmentation after some use time.
|
|
|
|
|
2010-07-04 07:36:23 -06:00
|
|
|
config TIDSPBRIDGE_RECOVERY
|
2010-07-04 07:36:24 -06:00
|
|
|
bool "Recovery Support"
|
2010-06-24 07:40:07 -06:00
|
|
|
depends on TIDSPBRIDGE
|
2010-07-04 07:36:24 -06:00
|
|
|
default y
|
2010-06-24 07:40:07 -06:00
|
|
|
help
|
|
|
|
In case of DSP fatal error, BRIDGE driver will try to
|
|
|
|
recover itself.
|
|
|
|
|
2010-07-04 07:36:23 -06:00
|
|
|
config TIDSPBRIDGE_CACHE_LINE_CHECK
|
2010-06-24 07:40:07 -06:00
|
|
|
bool "Check buffers to be 128 byte aligned"
|
|
|
|
depends on TIDSPBRIDGE
|
|
|
|
help
|
|
|
|
When the DSP processes data, the DSP cache controller loads 128-Byte
|
|
|
|
chunks (lines) from SDRAM and writes the data back in 128-Byte chunks.
|
|
|
|
If a DMM buffer does not start and end on a 128-Byte boundary, the data
|
|
|
|
preceding the start address (SA) from the 128-Byte boundary to the SA
|
|
|
|
and the data at addresses trailing the end address (EA) from the EA to
|
|
|
|
the next 128-Byte boundary will be loaded and written back as well.
|
|
|
|
This can lead to heap corruption. Say Y, to enforce the check for 128
|
|
|
|
byte alignment, buffers failing this check will be rejected.
|
|
|
|
|
2010-07-04 07:36:23 -06:00
|
|
|
config TIDSPBRIDGE_NTFY_PWRERR
|
2010-07-04 07:36:24 -06:00
|
|
|
bool "Notify power errors"
|
2010-06-24 07:40:07 -06:00
|
|
|
depends on TIDSPBRIDGE
|
|
|
|
help
|
2011-11-28 21:31:00 -07:00
|
|
|
Enable notifications to registered clients on the event of power error
|
2010-06-24 07:40:07 -06:00
|
|
|
trying to suspend bridge driver. Say Y, to signal this event as a fatal
|
|
|
|
error, this will require a bridge restart to recover.
|
2010-07-04 07:36:26 -06:00
|
|
|
|
|
|
|
config TIDSPBRIDGE_BACKTRACE
|
|
|
|
bool "Dump backtraces on fatal errors"
|
|
|
|
depends on TIDSPBRIDGE
|
|
|
|
help
|
|
|
|
Enable useful information to backtrace fatal errors. Say Y if you
|
|
|
|
want to dump information for testing purposes.
|