diff options
| author | Nishanth Menon | 2014-04-17 00:23:33 +0200 |
|---|---|---|
| committer | Nishanth Menon | 2014-05-05 21:34:15 +0200 |
| commit | cf52b2ecd719ca7acb19c0fd74bcfcce9dc6a362 (patch) | |
| tree | 5294ac9612de61175f949b89ea7e5c01f9737b93 /drivers/bus/omap_l3_noc.h | |
| parent | bus: omap_l3_noc: add information about the type of operation (diff) | |
| download | kernel-qcow2-linux-cf52b2ecd719ca7acb19c0fd74bcfcce9dc6a362.tar.gz kernel-qcow2-linux-cf52b2ecd719ca7acb19c0fd74bcfcce9dc6a362.tar.xz kernel-qcow2-linux-cf52b2ecd719ca7acb19c0fd74bcfcce9dc6a362.zip | |
bus: omap_l3_noc: Add information about the context of operation
L3 error may be triggered using Debug interface (example JTAG) or
due to other errors, for example an opcode fetch (due to function
pointer or stack corruption) or a data access (due to some other
failure). NOC registers contain additional information to help aid
debug information.
With this, we can enhance the error information to more detailed form:
"
L3 Custom Error: MASTER MPU TARGET L4PER2 (Read): Data Access in User mode
during Functional access
"
Signed-off-by: Nishanth Menon <nm@ti.com>
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Acked-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
Tested-by: Darren Etheridge <detheridge@ti.com>
Tested-by: Sekhar Nori <nsekhar@ti.com>
Diffstat (limited to 'drivers/bus/omap_l3_noc.h')
| -rw-r--r-- | drivers/bus/omap_l3_noc.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/bus/omap_l3_noc.h b/drivers/bus/omap_l3_noc.h index 6670fd98ce7c..36dc48b3dc00 100644 --- a/drivers/bus/omap_l3_noc.h +++ b/drivers/bus/omap_l3_noc.h @@ -31,7 +31,9 @@ #define L3_TARG_STDERRLOG_MAIN 0x48 #define L3_TARG_STDERRLOG_HDR 0x4c #define L3_TARG_STDERRLOG_MSTADDR 0x50 +#define L3_TARG_STDERRLOG_INFO 0x58 #define L3_TARG_STDERRLOG_SLVOFSLSB 0x5c +#define L3_TARG_STDERRLOG_CINFO_INFO 0x64 #define L3_TARG_STDERRLOG_CINFO_MSTADDR 0x68 #define L3_TARG_STDERRLOG_CINFO_OPCODE 0x6c #define L3_FLAGMUX_REGERR0 0xc |