vme: print unhandled VME access errors
authorDmitry Kalinkin <dmitry.kalinkin@gmail.com>
Thu, 17 Sep 2015 23:01:45 +0000 (02:01 +0300)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sun, 4 Oct 2015 18:50:57 +0000 (19:50 +0100)
This will enable error messages for accesses done through mmap.

Signed-off-by: Dmitry Kalinkin <dmitry.kalinkin@gmail.com>
Acked-by: Martyn Welch <martyn@welchs.me.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/vme/vme.c

index 7a10d926ebb47f681f7a2b1f01b43942b29cac7d..72924b0632b79c8eda73b06c51e2bdcc1b73634e 100644 (file)
@@ -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);