diff options
author | David S. Miller <davem@davemloft.net> | 2014-07-07 21:29:31 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2014-07-07 21:29:31 -0700 |
commit | 7cb9e6bfd691cf2af0078df9578f1da14a668324 (patch) | |
tree | bc6ddaa35868d042ece6bae97ac9c565fbe63231 /drivers/net/irda | |
parent | 1598c36afdd472560c1111cce473f8f88c747f14 (diff) | |
parent | 01ebd60b0ac64fc1f3a449ca29f2c02b37727967 (diff) | |
download | blackbird-obmc-linux-7cb9e6bfd691cf2af0078df9578f1da14a668324.tar.gz blackbird-obmc-linux-7cb9e6bfd691cf2af0078df9578f1da14a668324.zip |
Merge branch 'at86rf230-next'
Alexander Aring says:
====================
at86rf230: rework driver implementation
this patch series includes a rework of the at86rf230 driver.
There are several changes:
- Add regmap support.
- Merge at86rf212 operations with generic at86rf2xx operations, all chips
supports these operations.
- Drop of irqworker. This is a workqueue which will scheduled by an irq to
handle synchronous spi handling. Instead using asynchronous spi handling,
then no scheduler is involved at irq handling.
- Also detected some bugs by receiving frame like CRC can be correct and a
802.15.4 frame length could be above 127 bytes. This would crash the whole
kernel (but should be handled by the mac layer). Another bug is the handling
with RX_SAFE_MODE which protect the frame buffer after a readout. This is
currently not working because we read out the buffer twice and the first one
to get the frame size. Solution is to readout always the whole frame buffer.
- Added some timing relevants things from the datasheet for state changes And
IEEE 802.15.4 standard like interframe spacing. Interframe spacing is needed
to insert some receiving space time between frame transmitting. This should be
also handled by MAC layer, but it's currently a workaround to add this inside
the driver layer.
- Add some callback setting for chip specific handling, instead of runtime decisions
if (is_chip_type()). Callbacks are set only once at probe time.
- We don't using a force state change anymore. A force state change will do a
abort of receiving frames while we want to transmit a new frame. This should
decrease the drop rate of packets.
- And many others changes and bug fixes...
changes since v3:
- fix irq polarity in patch ("at86rf230: rework irq_pol setting").
changes since v2:
- add check if necessary functions are implemented when hw flags are set in patch
("mac802154: at86rf230: add hw flags and merge ops"). I choosed the second variant.
- remove unnecessary includes for workqueue and mutex in patch
("at86rf230: rework transmit and receive").
- remove unnecessary cast in patch ("at86rf230: rework transmit and receive").
- acivate regmap cache with REGCACHE_RBTREE in patch
("at86rf230: add regmap support").
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/irda')
0 files changed, 0 insertions, 0 deletions