The problem seams to be related to a timing issue when reading PM_WKST_WKUP, pulling for a daisy chain event. Introducing a simple mdelay(5) between the write and read operation fixes the problem but it is highly inefficient.
A real fix should follow shortly but in the mean time a kernel config with CONFIG_CPU_IDLE turned off has been checked in - this will allow people to keep working.
The problem seams to be related to a timing issue when reading PM_WKST_WKUP, pulling for a daisy chain event. Introducing a simple mdelay(5) between the write and read operation fixes the problem but it is highly inefficient.
A real fix should follow shortly but in the mean time a kernel config with CONFIG_CPU_IDLE turned off has been checked in - this will allow people to keep working.