Adrien suggested that all absolute axes events other than the hats should be recognised as axes and trigger the EVENT_GAMEPAD_AXIS.

Here are my observations for it:
* My gamepad is weird and evtest shows that it keeps signalling ABS_Z event even when nothing is pressed.
* The value of ABS_Z is ~127 but when I move around my left thumbstick, ABS_Z becomes equal to the value of ABS_X.

Hence, when I try to map my ABS_X to some input, I accidentally map ABS_Z to the next input.

(In reply to Abhinav Singh from comment #1)
> Here are my observations for it:
> * My gamepad is weird and evtest shows that it keeps signalling ABS_Z event
> even when nothing is pressed.
> * The value of ABS_Z is ~127 but when I move around my left thumbstick,
> ABS_Z becomes equal to the value of ABS_X.
> 
> Hence, when I try to map my ABS_X to some input, I accidentally map ABS_Z to
> the next input.

That's weird… but it looks like a bug in your gamepad itself, I'm not sure we can do anything about it. :/

Created attachment 354017 [details] [review]
gamepad: Send axis events for unhandled absolute axes

The axis events which weren't hats, X, Y, RX or RY wheren't handled and
ended up being sent as "nothing" events.

This make events from these unhandled axes be notified as axis events,
just like the ones from X, Y, RX and RY.

Attachment 354017 [details] pushed as a53a3cb - gamepad: Send axis events for unhandled absolute axes