1
linux/drivers/staging/tidspbridge
Omar Ramirez Luna 08cd9ef4ec staging: tidspbridge: detect wdt3 feature at runtime
In order to detect WDT feature on the dsp code, we need to
find the symbol used to enable it inside the baseimage.

This should fix the warning comming from L3 driver:

    WARNING: at arch/arm/mach-omap2/omap_l3_smx.c:161 omap3_l3_app_irq...
    In-band Error seen by IVA_SS  at address 0
    ...

That occurs because the dsp tries to access wdt3 registers when the clock
for those registers is not enabled.

Reported-by: Felipe Contreras <felipe.contreras@gmail.com>
Signed-off-by: Omar Ramirez Luna <omar.ramirez@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2012-02-24 12:05:38 -08:00
..
core staging: tidspbridge: detect wdt3 feature at runtime 2012-02-24 12:05:38 -08:00
Documentation
dynload Revert wrong fixes for common misspellings 2011-04-26 23:31:11 -07:00
gen staging: tidspbridge: remove dbc.h 2012-02-09 09:38:19 -08:00
hw staging: tidspbridge: MMU2 registers are limited to 32-bit data access 2011-10-19 13:42:49 -07:00
include/dspbridge staging: tidspbridge: always compile dsp wdt code 2012-02-24 12:05:38 -08:00
pmgr staging: tidspbridge: remove dbc.h 2012-02-09 09:38:19 -08:00
rmgr staging: tidspbridge: fix bridge_open memory leaks 2012-02-14 15:38:51 -08:00
Kconfig staging: tidspbridge: always compile dsp wdt code 2012-02-24 12:05:38 -08:00
Makefile staging: tidspbridge: Rename module from bridgedriver to tidspbridge 2012-02-09 09:37:11 -08:00
TODO