projects / linux-2.6-block.git / blame
| Commit | Line | Data |
|---|---|---|
| cbf05091 ORL |
1 | # |
| 2 | # DSP Bridge Driver Support | |
| 3 | # | |
| 4 | ||
| 5 | menuconfig TIDSPBRIDGE | |
| 6 | tristate "DSP Bridge driver" | |
| a62a6e98 | 7 | depends on ARCH_OMAP3 && !ARCH_MULTIPLATFORM |
| c869c75c SA |
8 | select MAILBOX |
| 9 | select OMAP2PLUS_MBOX | |
| cbf05091 ORL |
10 | help |
| 11 | DSP/BIOS Bridge is designed for platforms that contain a GPP and | |
| 12 | one or more attached DSPs. The GPP is considered the master or | |
| 13 | "host" processor, and the attached DSPs are processing resources | |
| 14 | that can be utilized by applications and drivers running on the GPP. | |
| 15 | ||
| 16 | This driver depends on OMAP Mailbox (OMAP_MBOX_FWK). | |
| 17 | ||
| b3d23688 | 18 | config TIDSPBRIDGE_DVFS |
| cbf05091 ORL |
19 | bool "Enable Bridge Dynamic Voltage and Frequency Scaling (DVFS)" |
| 20 | depends on TIDSPBRIDGE && OMAP_PM_SRF && CPU_FREQ | |
| cbf05091 ORL |
21 | help |
| 22 | DVFS allows DSP Bridge to initiate the operating point change to | |
| 23 | scale the chip voltage and frequency in order to match the | |
| 24 | performance and power consumption to the current processing | |
| 25 | requirements. | |
| 26 | ||
| b3d23688 | 27 | config TIDSPBRIDGE_MEMPOOL_SIZE |
| cbf05091 ORL |
28 | hex "Physical memory pool size (Byte)" |
| 29 | depends on TIDSPBRIDGE | |
| 30 | default 0x600000 | |
| 31 | help | |
| 32 | Allocate specified size of memory at booting time to avoid allocation | |
| 33 | failure under heavy memory fragmentation after some use time. | |
| 34 | ||
| b3d23688 | 35 | config TIDSPBRIDGE_RECOVERY |
| ed9ff5d7 | 36 | bool "Recovery Support" |
| cbf05091 | 37 | depends on TIDSPBRIDGE |
| ed9ff5d7 | 38 | default y |
| cbf05091 ORL |
39 | help |
| 40 | In case of DSP fatal error, BRIDGE driver will try to | |
| 41 | recover itself. | |
| 42 | ||
| b3d23688 | 43 | config TIDSPBRIDGE_CACHE_LINE_CHECK |
| cbf05091 ORL |
44 | bool "Check buffers to be 128 byte aligned" |
| 45 | depends on TIDSPBRIDGE | |
| cbf05091 ORL |
46 | help |
| 47 | When the DSP processes data, the DSP cache controller loads 128-Byte | |
| 48 | chunks (lines) from SDRAM and writes the data back in 128-Byte chunks. | |
| 49 | If a DMM buffer does not start and end on a 128-Byte boundary, the data | |
| 50 | preceding the start address (SA) from the 128-Byte boundary to the SA | |
| 51 | and the data at addresses trailing the end address (EA) from the EA to | |
| 52 | the next 128-Byte boundary will be loaded and written back as well. | |
| 53 | This can lead to heap corruption. Say Y, to enforce the check for 128 | |
| 54 | byte alignment, buffers failing this check will be rejected. | |
| 55 | ||
| b3d23688 | 56 | config TIDSPBRIDGE_NTFY_PWRERR |
| ed9ff5d7 | 57 | bool "Notify power errors" |
| cbf05091 ORL |
58 | depends on TIDSPBRIDGE |
| 59 | help | |
| 42b2aa86 | 60 | Enable notifications to registered clients on the event of power error |
| cbf05091 ORL |
61 | trying to suspend bridge driver. Say Y, to signal this event as a fatal |
| 62 | error, this will require a bridge restart to recover. | |
| 4f551c8f FC |
63 | |
| 64 | config TIDSPBRIDGE_BACKTRACE | |
| 65 | bool "Dump backtraces on fatal errors" | |
| 66 | depends on TIDSPBRIDGE | |
| 67 | help | |
| 68 | Enable useful information to backtrace fatal errors. Say Y if you | |
| 69 | want to dump information for testing purposes. |