From drivers/mmc/host/mvsdio.c:492, this interrupt is an unexpected one, which cannot be recognized and processed correctly by all branches of code within this handler. So either this handler is not well designed to miss this interrupt, or it meets an unexpected hw error.
For the former case, we can do nothing but to push the SOC vendor to test and solve it;
For the latter case, we can change another known-well SD card, as well as another armadaxp board to see if this is related to the specific SD card (or board).
I'll let Marvell guys know this bug; and at the same time, could anybody test another SD card and board? Thanks!
From drivers/ mmc/host/ mvsdio. c:492, this interrupt is an unexpected one, which cannot be recognized and processed correctly by all branches of code within this handler. So either this handler is not well designed to miss this interrupt, or it meets an unexpected hw error.
For the former case, we can do nothing but to push the SOC vendor to test and solve it;
For the latter case, we can change another known-well SD card, as well as another armadaxp board to see if this is related to the specific SD card (or board).
I'll let Marvell guys know this bug; and at the same time, could anybody test another SD card and board? Thanks!