drivers/staging/tidspbridge/Kconfig

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