Date: | 2011-07-07 15:15:31 (12 years 8 months ago) |
---|---|
Author: | Werner Almesberger |
Commit: | e21c6ed8f48f10726f75d5f02f57f2a3c510e15a |
Message: | at86rf230: we may be in BUSY_RX after commanding RX_ON Checking arrival in RX_ON races with incoming traffic. If frame reception begins before we have a chance to see that we've arrived in RX_ON, at86rf230_state complains about unexpectedly finding the transceiver in BUSY_RX. This isn't the prettiest solution (and it doesn't check if we're in BUSY_RX before even commanding the change, although I think this shouldn't happen), but it makes the problem go away. Signed-off-by: Werner Almesberger <werner@almesberger.net> |
Files: |
drivers/ieee802154/at86rf230.c (1 diff) |
Change Details
drivers/ieee802154/at86rf230.c | ||
---|---|---|
322 | 322 | |
323 | 323 | if (val == desired_status) |
324 | 324 | return 0; |
325 | if (state == STATE_RX_ON && val == STATE_BUSY_RX) | |
326 | return 0; | |
325 | 327 | |
326 | 328 | pr_err("%s unexpected state change: %d, asked for %d\n", __func__, |
327 | 329 | val, state); |
Branches:
ben-wpan
ben-wpan-stefan
5396a9238205f20f811ea57898980d3ca82df0b6
jz-2.6.34
jz-2.6.34-rc5
jz-2.6.34-rc6
jz-2.6.34-rc7
jz-2.6.35
jz-2.6.36
jz-2.6.37
jz-2.6.38
jz-2.6.39
jz-3.0
jz-3.1
jz-3.11
jz-3.12
jz-3.13
jz-3.15
jz-3.16
jz-3.18-dt
jz-3.2
jz-3.3
jz-3.4
jz-3.5
jz-3.6
jz-3.6-rc2-pwm
jz-3.9
jz-3.9-clk
jz-3.9-rc8
jz47xx
jz47xx-2.6.38
master
Tags:
od-2011-09-04
od-2011-09-18
v2.6.34-rc5
v2.6.34-rc6
v2.6.34-rc7
v3.9