summaryrefslogtreecommitdiffstats
path: root/include/linux/nl802154.h
diff options
context:
space:
mode:
authorPhoebe Buckheister <phoebe.buckheister@itwm.fraunhofer.de>2014-02-17 11:34:13 +0100
committerDavid S. Miller <davem@davemloft.net>2014-02-17 16:42:39 -0500
commit7dcbd22a97eb0689e6c583ad630ae0e7341e34c1 (patch)
treef78ea0f4c4de05f679311451745f7540c229b86f /include/linux/nl802154.h
parent6ca001978dce0d50ebac01a38d6287f241a520c6 (diff)
downloadlinux-stable-7dcbd22a97eb0689e6c583ad630ae0e7341e34c1.tar.gz
linux-stable-7dcbd22a97eb0689e6c583ad630ae0e7341e34c1.tar.bz2
linux-stable-7dcbd22a97eb0689e6c583ad630ae0e7341e34c1.zip
ieee802154: ensure that first RF212 state comes from TRX_OFF
A documented erratum of the RF212 chip describes that some versions of RF212 may not be properly reset by the standard reset procedure. The described workaround seems to not fully work either; my RF212 chips will not correctly receive any frames unless they are taken from RX mode to TRX_OFF and back to RX mode, effectively forcing a up-down-up-cycle. Going to TRX_OFF and to RX without intermediate state changes at least once fixes this. The same transition is allowed for RF230, so simply do it all the time. Signed-off-by: Phoebe Buckheister <phoebe.buckheister@itwm.fraunhofer.de> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/linux/nl802154.h')
0 files changed, 0 insertions, 0 deletions