Hi, On Wed, Aug 2, 2017 at 6:16 PM, Alexander Aring <aring@xxxxxxxxxxxx> wrote: > Hi, > ... >> >> It's "... to another state."... Maybe when a RX irq occurs during the >> spi async handling there could be some "xmit" callbacks... This will >> change the transceiver into another state... (not directly, but so far >> I know it queues for state change). So when it will automatically go >> into RX_AACK_ON then it will change the state to something else and >> allows framebuffer overwrite. > > it could be that there exists a race when stop queue is running and > currently a xmit is going on... > I currently have no idea how to solve it and need to have more details > what happens when the transceiver is in BUSY_RX and we do another > state change? Will it be queued or not (so after BUSY_RX it will > change to RX_ON and then another state)? > Sorry, I remember... you told you don't send anything? Then this can't be the issue. :-( ... but maybe we should stop transmit queue while receiving. - Alex -- To unsubscribe from this list: send the line "unsubscribe linux-wpan" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
