From: Thomas Stilwell <stilwellt@openlabs.co>
To: linux-zigbee-devel@lists.sourceforge.net
Cc: Alexander Aring <alex.aring@gmail.com>,
alex.bluesman.smirnov@gmail.com, netdev@vger.kernel.org
Subject: Re: [Linux-zigbee-devel] [PATCH net-next 00/13] at86rf230: rework driver implementation
Date: Tue, 01 Jul 2014 02:14:46 -0500 [thread overview]
Message-ID: <2413759.FQMUtNpPHP@neo> (raw)
In-Reply-To: <1403980431-6201-1-git-send-email-alex.aring@gmail.com>
On Saturday 28 June 2014 20:33:38 Alexander Aring wrote:
> Hi,
>
> 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...
>
>
> - Alex
>
> Alexander Aring (13):
> mac802154: at86rf230: add hw flags and merge ops
> at86rf230: add regmap support
> at86rf230: rework detect device handling
> at86rf230: remove is212 and add driver data
> at86rf230: add support for at86rf23x desense
> at86rf230: rework transmit and receive handling
> at86rf230: move RX_SAFE_MODE setting to hw_init
> at86rf230: rework irq_pol setting
> at86rf230: rework state change and start/stop
> at86rf230: rework reset to trx_off state change
> at86rf230: add timing for channel switch
> at86rf230: add sleep cycle timing
> at86rf230: add new author
>
> drivers/net/ieee802154/Kconfig | 1 +
> drivers/net/ieee802154/at86rf230.c | 1464
> +++++++++++++++++++++++------------- include/net/mac802154.h |
> 19 +
> net/mac802154/ieee802154_dev.c | 12 +-
> 4 files changed, 951 insertions(+), 545 deletions(-)
Tested with at86rf233
Tested-by: Thomas Stilwell <stilwellt@openlabs.co>
prev parent reply other threads:[~2014-07-01 7:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 18:33 [PATCH net-next 00/13] at86rf230: rework driver implementation Alexander Aring
2014-06-28 18:33 ` [PATCH net-next 02/13] at86rf230: add regmap support Alexander Aring
2014-06-28 18:33 ` [PATCH net-next 05/13] at86rf230: add support for at86rf23x desense Alexander Aring
2014-06-28 18:33 ` [PATCH net-next 08/13] at86rf230: rework irq_pol setting Alexander Aring
2014-06-28 18:33 ` [PATCH net-next 09/13] at86rf230: rework state change and start/stop Alexander Aring
2014-06-28 18:33 ` [PATCH net-next 12/13] at86rf230: add sleep cycle timing Alexander Aring
[not found] ` <1403980431-6201-1-git-send-email-alex.aring-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-06-28 18:33 ` [PATCH net-next 01/13] mac802154: at86rf230: add hw flags and merge ops Alexander Aring
2014-07-02 6:14 ` David Miller
2014-06-28 18:33 ` [PATCH net-next 03/13] at86rf230: rework detect device handling Alexander Aring
2014-06-28 18:33 ` [PATCH net-next 04/13] at86rf230: remove is212 and add driver data Alexander Aring
2014-06-28 18:33 ` [PATCH net-next 06/13] at86rf230: rework transmit and receive handling Alexander Aring
2014-06-28 18:33 ` [PATCH net-next 07/13] at86rf230: move RX_SAFE_MODE setting to hw_init Alexander Aring
2014-06-28 18:33 ` [PATCH net-next 10/13] at86rf230: rework reset to trx_off state change Alexander Aring
2014-06-28 18:33 ` [PATCH net-next 11/13] at86rf230: add timing for channel switch Alexander Aring
2014-06-28 18:33 ` [PATCH net-next 13/13] at86rf230: add new author Alexander Aring
2014-07-01 7:14 ` Thomas Stilwell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2413759.FQMUtNpPHP@neo \
--to=stilwellt@openlabs.co \
--cc=alex.aring@gmail.com \
--cc=alex.bluesman.smirnov@gmail.com \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).