roadrunner2

@shrijitsingh99 Thanks for running this and getting the output. It confirms what I stated earlier: the spi message is being queued in the spi core, but for some reason the...

@TheChatty (or anybody else interested): I was just wondering if for some reason the keyboard's SPI interface needs to be forcefully re-enabled after resume on the MB8,1 (from my reading...

@denisix Looking at the dmesg.fail log, it looks like you are unloading `applespi` and some of the pxa2xx modules before suspend and loading them again after resume? Can you tell...

Pleae check out the instructions in [my gist](https://gist.github.com/roadrunner2/1289542a748d9a104e7baec6a92f9cd7).

This sounds like the known issue with the interrupt (21 on your system) on MB8,1 and needing `irqpoll`. Can you search for other mentions of interrupt 21 in your dmesg...

Btw., does using `irqfixup` instead of `irqpoll` also "fix" the issue? That would appear to be a lighter weight hack. As to what exactly the problem is with the (not)...

> In any case (e.g. keyboard working) the keyboard is not lit up - is that expected? No, it isn't, though I'm not 100% sure if anybody else has tested...

Regarding the keyboard brightness working manually: if you unload and reload the `applespi` module, or just load it later, then the keyboard brightness keys will stop working (in Gnome, at...

> After suspend I am unable to remove the module. `rmmod applespi` just hangs. I think I see the problem (missed clearing some flags on a read error) and pushed...

So there are two distinct issues with the keyboard/touchpad on MB8,1: 1. the system sometimes/often needs to be booted with `irqfixup` (this issue) 2. the keyboard/touchpad is non-functional after resume...