The rf233 and rf231 are sufficiently similar that we can treat
rf233 like rf231.
rf233 is missing some features that rf231 has, but we don't currently
make use of them so there's nothing to handle differently yet.
Should we add support in the future for rf231 *_NOCLK or SLEEP states,
or PAD_IO drive strength, exceptions will need to be made for rf233.
Signed-off-by: Thomas Stilwell <stilwellt@openlabs.co>
Signed-off-by: David S. Miller <davem@davemloft.net>
config IEEE802154_AT86RF230
depends on IEEE802154_DRIVERS && MAC802154
- tristate "AT86RF230/231/212 transceiver driver"
+ tristate "AT86RF230/231/233/212 transceiver driver"
depends on SPI
---help---
- Say Y here to enable the at86rf230/231/212 SPI 802.15.4 wireless
+ Say Y here to enable the at86rf230/231/233/212 SPI 802.15.4 wireless
controller.
This driver can also be built as a module. To do so, say M here.
#define STATE_TX_ON 0x09
/* 0x0a - 0x0e */ /* 0x0a - UNSUPPORTED_ATTRIBUTE */
#define STATE_SLEEP 0x0F
+#define STATE_PREP_DEEP_SLEEP 0x10
#define STATE_BUSY_RX_AACK 0x11
#define STATE_BUSY_TX_ARET 0x12
#define STATE_RX_AACK_ON 0x16
if (version == 1)
ops = &at86rf212_ops;
break;
+ case 11:
+ chip = "at86rf233";
+ ops = &at86rf230_ops;
+ break;
default:
chip = "UNKNOWN";
break;