From: Varka Bhadram <varkabhadram@gmail.com>
To: Alexander Aring <alex.aring@gmail.com>, linux-wpan@vger.kernel.org
Cc: kernel@pengutronix.de
Subject: Re: [PATCHv2 wpan-next 4/6] at86rf230: remove unnecessary tx state change
Date: Wed, 29 Apr 2015 14:21:04 +0530 [thread overview]
Message-ID: <55409B78.8050002@gmail.com> (raw)
In-Reply-To: <1430292893-5752-5-git-send-email-alex.aring@gmail.com>
On 04/29/2015 01:04 PM, Alexander Aring wrote:
> All supported transceivers can do a valid state change from TRX_OFF to
> AACK_ON. This patach removes the state change chain from TRX_OFF ->
s/patach/patch
> TX_ON -> AACK_ON instead we doing a directly state change from TRX_OFF
> to AACK_ON.
>
> Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> ---
> drivers/net/ieee802154/at86rf230.c | 16 +++-------------
> 1 file changed, 3 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/net/ieee802154/at86rf230.c b/drivers/net/ieee802154/at86rf230.c
> index f99dce5..6285145 100644
> --- a/drivers/net/ieee802154/at86rf230.c
> +++ b/drivers/net/ieee802154/at86rf230.c
> @@ -781,16 +781,6 @@ at86rf230_tx_on(void *context)
> }
>
> static void
> -at86rf230_tx_trac_error(void *context)
> -{
> - struct at86rf230_state_change *ctx = context;
> - struct at86rf230_local *lp = ctx->lp;
> -
> - at86rf230_async_state_change(lp, ctx, STATE_TX_ON,
> - at86rf230_tx_on, true);
> -}
> -
> -static void
> at86rf230_tx_trac_check(void *context)
> {
> struct at86rf230_state_change *ctx = context;
> @@ -799,12 +789,12 @@ at86rf230_tx_trac_check(void *context)
> const u8 trac = (buf[1] & 0xe0) >> 5;
>
> /* If trac status is different than zero we need to do a state change
> - * to STATE_FORCE_TRX_OFF then STATE_TX_ON to recover the transceiver
> - * state to TX_ON.
> + * to STATE_FORCE_TRX_OFF then STATE_RX_AACK_ON to recover the
> + * transceiver.
> */
> if (trac)
> at86rf230_async_state_change(lp, ctx, STATE_FORCE_TRX_OFF,
> - at86rf230_tx_trac_error, true);
> + at86rf230_tx_on, true);
> else
> at86rf230_tx_on(context);
> }
--
Varka Bhadram
next prev parent reply other threads:[~2015-04-29 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 7:34 [PATCHv2 wpan-next 0/6] at86rf230: cleanups and transmit improvements Alexander Aring
2015-04-29 7:34 ` [PATCHv2 wpan-next 1/6] at86rf230: remove tabs after define Alexander Aring
2015-04-29 7:34 ` [PATCHv2 wpan-next 2/6] at86rf230: move cal_timeout to state change Alexander Aring
2015-04-29 7:34 ` [PATCHv2 wpan-next 3/6] at86rf230: add TX_ARET_ON for calibration timeout Alexander Aring
2015-04-29 7:34 ` [PATCHv2 wpan-next 4/6] at86rf230: remove unnecessary tx state change Alexander Aring
2015-04-29 8:51 ` Varka Bhadram [this message]
2015-04-29 7:34 ` [PATCHv2 wpan-next 5/6] at86rf230: change state change if from trx_off Alexander Aring
2015-04-29 7:34 ` [PATCHv2 wpan-next 6/6] at86rf230: add slp_tr support to start tx Alexander Aring
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=55409B78.8050002@gmail.com \
--to=varkabhadram@gmail.com \
--cc=alex.aring@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-wpan@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