msm: Optionally report L2 master port errors to kernel log
Certain operations may generate large numbers of L2 master
port slave/decode errors, flooding the kernel log unless
explicitly disabled.
Change-Id: I3b4606e39530b15a6af4999aaead14bd2b4ea2d3
Signed-off-by: Stepan Moskovchenko <stepanm@codeaurora.org>
diff --git a/arch/arm/mach-msm/Kconfig b/arch/arm/mach-msm/Kconfig
index 9cf07fc..e94ad3a 100644
--- a/arch/arm/mach-msm/Kconfig
+++ b/arch/arm/mach-msm/Kconfig
@@ -2192,10 +2192,23 @@
For production builds, you should probably say 'N' here.
+config MSM_L2_ERP_PRINT_ACCESS_ERRORS
+ bool "Report L2 master port slave/decode errors in kernel log"
+ depends on MSM_CACHE_ERP
+ help
+ Master port errors can occur when a memory request is not properly
+ handled by the destination slave. This can occur if the destination
+ register does not exist or is inaccessible due to security
+ restrictions or (in some cases) clock configuration. Enabling this
+ option will cause a backtrace to be printed to the kernel log whenever
+ such an error is encountered. Note that the error is reported as an
+ interrupt rather than as an exception, meaning that the backtrace may
+ have some skid. This option may help with debugging, though production
+ builds should probably say 'N' here.
config MSM_L2_ERP_PORT_PANIC
bool "Panic on L2 master port errors"
- depends on MSM_CACHE_ERP
+ depends on MSM_CACHE_ERP && MSM_L2_ERP_PRINT_ACCESS_ERRORS
help
Master port errors can occur when a memory request is not properly
handled by the destination slave. Enable this option to catch drivers