[RESEND 4/4] vme: print unhandled VME access errors
Martyn Welch
martyn at welchs.me.uk
Fri Sep 18 09:48:32 UTC 2015
On 18/09/15 00:01, dmitry.kalinkin at gmail.com wrote:
> From: Dmitry Kalinkin <dmitry.kalinkin at gmail.com>
>
> This will enable error messages for accesses done through mmap.
>
> Signed-off-by: Dmitry Kalinkin <dmitry.kalinkin at gmail.com>
Acked-by: Martyn Welch <martyn at welchs.me.uk>
> ---
> drivers/vme/vme.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/vme/vme.c b/drivers/vme/vme.c
> index 7a10d92..72924b0 100644
> --- a/drivers/vme/vme.c
> +++ b/drivers/vme/vme.c
> @@ -1028,6 +1028,7 @@ void vme_bus_error_handler(struct vme_bridge *bridge,
> {
> struct list_head *handler_pos = NULL;
> struct vme_error_handler *handler;
> + int handler_triggered = 0;
> u32 aspace = vme_get_aspace(am);
>
> list_for_each(handler_pos, &bridge->vme_error_handlers) {
> @@ -1040,8 +1041,14 @@ void vme_bus_error_handler(struct vme_bridge *bridge,
> handler->first_error = address;
> if (handler->num_errors != UINT_MAX)
> handler->num_errors++;
> + handler_triggered = 1;
> }
> }
> +
> + if (!handler_triggered)
> + dev_err(bridge->parent,
> + "Unhandled VME access error at address 0x%llx\n",
> + address);
> }
> EXPORT_SYMBOL(vme_bus_error_handler);
>
More information about the devel
mailing list