Benjamin Valentin 853bbaf5a5 drivers/mrf24j40: don't loop in mrf24j40_reset_state_machine() ... When hooking up the mrf24j40 to a bluepill board, the driver would always get stuck on init. Debugging revealed that it would get stuck in the mrf24j40_reset_state_machine() function because it expects the RFSTATE to have a special value after reset. However, the data sheet does not mention this in section 3.1 Reset. Waiting 192µs should be enough - the value of the RFSTATE is not specified. The Linux driver also does not wait for the RFSTATE register. And even without the loop, the driver is functioning fine.		2019-10-11 23:01:54 +02:00
..
include	drivers/mrf24j40 : support of NETOPT_LAST_ED_LEVEL	2019-05-23 15:45:03 +02:00
Makefile	drivers/mrf24j40: initial mrf24j40 support	2017-01-26 10:05:20 +01:00
mrf24j40_getset.c	drivers/mrf24j40: don't loop in mrf24j40_reset_state_machine()	2019-10-11 23:01:54 +02:00
mrf24j40_internal.c	drivers/mrf24j40: add external PA/LNA control on MC/MD/ME devices	2019-05-23 11:07:04 +02:00
mrf24j40_netdev.c	drivers/mrf24j40 : support of NETOPT_LAST_ED_LEVEL	2019-05-23 15:45:03 +02:00
mrf24j40.c	drivers/mrf24j40 : support of NETOPT_LAST_ED_LEVEL	2019-05-23 15:45:03 +02:00