24 Sep, 2011
2 commits
-
The indentation problems in the l3 noc and smx
error handler files are fixed.Signed-off-by: sricharan
Signed-off-by: Santosh Shilimkar
Reported-by: Paul Walmsley -
* Changed the way of accessing L3 target
registers from standard base rather
than relative to STDERRLOG_MAIN.* Use ffs() to find error source from
the L3_FLAGMUX_REGERRn register.* Remove extra l3_base[] entry.
* Modified L3 custom error message.
Signed-off-by: Todd Poynor
Signed-off-by: sricharan
Signed-off-by: Santosh Shilimkar
17 May, 2011
1 commit
03 May, 2011
2 commits
-
Removing extra lines, spaces and unneeded parenthesis.
Collapsing an if statement to detect the type of error.l3_smx:
- Fixing the message printed on error.So now: looks like:
"No Error Error seen..." "No Error seen..."
"In-Band Error Error seen..." "In-Band Error seen..."Other messages are self explanatory, no "Error" added to them.
(E.g.: "Address Hole seen...")Signed-off-by: Omar Ramirez Luna
Acked-by: Santosh Shilimkar
Signed-off-by: Tony Lindgren -
l3_smx:
- Add missing free_irq and remove an empty goto label.l3_noc:
- If kzalloc fails driver shouldn't continue with a NULL pointer.
- Add missing free_irq and remove empty goto labels.
- Safe to assume that if we reached the end point of execution
without errors, then return value is 0, so replacing instead
another goto.Signed-off-by: Omar Ramirez Luna
Acked-by: Santosh Shilimkar
Signed-off-by: Tony Lindgren
26 Apr, 2011
1 commit
-
If an error occurs in the L3 on any other initiator than MPU,
the interrupt goes unhandled given that the 'base' register
was calculated with the initialized err_source value (which
coincidentally points to MPU) and not with the actual source
of the error.Removed parenthesis that are not needed for the touched lines.
Signed-off-by: Omar Ramirez Luna
Acked-by: Santosh Shilimkar
Signed-off-by: Tony Lindgren
19 Mar, 2011
1 commit
-
The handler function may be called from the point it is registered.
Since the handler inspects IRQ numbers, we must set them up before
registration.Signed-off-by: Aaro Koskinen
Acked-by: Santosh Shilimkar
Signed-off-by: Tony Lindgren
09 Mar, 2011
1 commit
-
The driver provides the information regarding the ocp errors
that gets logged in the interconnect.The error info provides
the details regarding the master or the target that
generated the error, type of error and the corresponding address.
The stack dump is also provided.Signed-off-by: sricharan
[r.sricharan@ti.com: Enhacements, major cleanup and made it functional]
Signed-off-by: Santosh Shilimkar
[santosh.shilimkar@ti.com: Driver design changes as per OMAP4 version]
Signed-off-by: Felipe Balbi
[balbi@ti.com: Initial version of the driver]
Acked-by: Benoit Cousson