All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Stefan Schmidt <stefan@osg.samsung.com>
Cc: linux-wpan@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [RFC bluetooth-next 1/2] at86rf230: change trac status check behaviour
Date: Thu, 27 Aug 2015 12:13:20 +0200	[thread overview]
Message-ID: <20150827101318.GA2609@omega> (raw)
In-Reply-To: <55DEDEDB.1010302@osg.samsung.com>

On Thu, Aug 27, 2015 at 11:56:43AM +0200, Stefan Schmidt wrote:
> Hello.
> 
> On 06/08/15 17:21, Alexander Aring wrote:
> >When transmit is done, indicated by trx_end irq, we do first a force
> >state change to TX_ON and then checking the trac status, if the trac
> >status is unequal zero we do a state change to TRX_OFF.
> >
> >This patch changes to the following behaviour, we first check on trac
> >status after trx_end occurs and then doing a normal change to TX_ON
> >without do the state change to TRX_OFF when trac status is unequal zero.
> >
> >The reasons are that the datasheet doesn't described when the trac
> >status register is cleared, we should doing to evaluate the trac status
> >at first. The reason to remove the TRX_OFF change if the trac status is
> >unequal to zero and it was force is the following paragraph inside The
> >at86rf2xx datasheets:
> >
> >"Using FORCE_PLL_ON to interrupt an TX_ARET transaction, it is
> >  recommended to check register bits [7:5] of register address 0x32 for
> >  value 0. If this value is different, TRX_CMD sequence FORCE_TRX_OFF shall
> >  be used immediately followed by TRX_CMD sequence PLL_ON. This performs a
> >  state transition to PLL_ON."
> I had a hard time finding a register description of 0x32 in my copies. Are
> they outdated or am I just blind? Any hints appreciated. :)
> 

I think this is a mistake in the datasheet, they mean the "TRAC_STATUS"
here, which is the only value which fits in the range of [7:5] in
Register 0x02.

Nevertheless this handling is for interrupt the TX_ARET transaction,
then maybe this would be more fit if we do a that on the only once
FORCE_TX_ON change, this is at [0] when the maximum of "trying to change
into TX_ON is reached".

This case is very unlikely I would simple move always to FORCE_TRX_OFF
when interrupt any TX_*ON state. From TRX_OFF you can reach
RX_AACK_ON/TX_*ON states on all at86rf2xx(except 230 which we don't
support) transceivers

- Alex

[0] http://lxr.free-electrons.com/source/drivers/net/ieee802154/at86rf230.c#L558

  reply	other threads:[~2015-08-27 10:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 15:21 [RFC bluetooth-next 0/2] at86rf230: trac debugfs support (for testing aret changes patch-serie) Alexander Aring
2015-08-06 15:21 ` [RFC bluetooth-next 1/2] at86rf230: change trac status check behaviour Alexander Aring
2015-08-27  9:56   ` Stefan Schmidt
2015-08-27 10:13     ` Alexander Aring [this message]
2015-08-27 12:23       ` Stefan Schmidt
2015-08-27 12:31         ` Alexander Aring
2015-08-27 12:56           ` Stefan Schmidt
2015-08-06 15:21 ` [RFC bluetooth-next 2/2] at86rf230: add debugfs support Alexander Aring
2015-08-27  9:53   ` Stefan Schmidt
2015-08-27  9:58 ` [RFC bluetooth-next 0/2] at86rf230: trac debugfs support (for testing aret changes patch-serie) Stefan Schmidt

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=20150827101318.GA2609@omega \
    --to=alex.aring@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-wpan@vger.kernel.org \
    --cc=stefan@osg.samsung.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.