xtensa: Remove _xt_set_exception_handler()

This was a dead API.  Nothing ever used it, it wasn't exposed in any
API headers.  It never appeared in documentation.  It's not
particularly clear why a Zephy app would want to hook
architecture-specific exceptions instead of simply using the portable
error framework anyway. And it's not supported by asm2.  Delete.

Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
This commit is contained in:
Andy Ross 2017-12-14 09:58:43 -08:00 committed by Anas Nashif
commit a0dd2de6fd
2 changed files with 2 additions and 25 deletions

View file

@ -23,6 +23,8 @@ static void unhandled_exception_trampoline(XtExcFrame *frame)
CODE_UNREACHABLE;
}
typedef void (*xt_exc_handler)(XtExcFrame *);
xt_exc_handler _xt_exception_table[XCHAL_EXCCAUSE_NUM] __aligned(4) = {
[0 ... (XCHAL_EXCCAUSE_NUM - 1)] = unhandled_exception_trampoline
};

View file

@ -10,31 +10,6 @@
#include "xtensa_rtos.h"
#include "xtensa_context.h"
/* Typedef for C-callable interrupt handler function */
typedef void (*xt_handler)(void *);
/* Typedef for C-callable exception handler function */
typedef void (*xt_exc_handler)(XtExcFrame *);
/*
* Call this function to set a handler for the specified exception.
*
* n - Exception number (type) f - Handler function address,
* NULL to uninstall handler.
*
* The handler will be passed a pointer to the exception frame, which is created
* on the stack of the thread that caused the exception.
*
* If the handler returns, the thread context will be restored and the faulting
* instruction will be retried. Any values in the exception frame that are
* modified by the handler will be restored as part of the context. For details
* of the exception frame structure see xtensa_context.h.
*
* FIXME: Remove this API entirely
*/
extern xt_exc_handler _xt_set_exception_handler(int n, xt_exc_handler f);
/*
* Call this function to enable the specified interrupts.
*