From: Alexander Aring <alex.aring@gmail.com>
To: Varka Bhadram <varkabhadram@gmail.com>
Cc: linux-wpan@vger.kernel.org, Varka Bhadram <varkab@cdac.in>
Subject: Re: [PATCH bluetooth-next 3/3] cc2520: fix in updated register settings
Date: Fri, 20 Mar 2015 16:38:04 +0100 [thread overview]
Message-ID: <20150320153800.GC3952@omega> (raw)
In-Reply-To: <1426836141-21528-3-git-send-email-varkab@cdac.in>
Hi,
On Fri, Mar 20, 2015 at 12:52:20PM +0530, Varka Bhadram wrote:
> This patch fix the updated register settings for transmit power.
>
> As per the datasheet [section 28.1 Register Settings Update]
> the transmit power register value has to be updated to 0x32 (0 dBm)
> from the default value.
>
> CC2520_TXPOWER_4 indicates the value 0x32 (0 dBm).
>
> Signed-off-by: Varka Bhadram <varkab@cdac.in>
> ---
> drivers/net/ieee802154/cc2520.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ieee802154/cc2520.c b/drivers/net/ieee802154/cc2520.c
> index f96cc50..d9135ec 100644
> --- a/drivers/net/ieee802154/cc2520.c
> +++ b/drivers/net/ieee802154/cc2520.c
> @@ -860,7 +860,8 @@ static int cc2520_hw_init(struct cc2520_private *priv)
> if (ret)
> goto err_ret;
> } else {
> - ret = cc2520_write_register(priv, CC2520_TXPOWER, 0xF7);
> + ret = cc2520_write_register(priv, CC2520_TXPOWER,
> + CC2520_TXPOWER_4);
> if (ret)
> goto err_ret;
you also need to set _always_ the default phy value after reset in the
wpan_phy struct.
Example:
/* sets default transmit_power */
foobar->hw->phy->transmit_power = 4;
otherwise the phy layer doesn't know the initial txpower. In cc2520
there is also a missing initial value for the CCA mode. There must be
running some CCA mode which also stands in the datasheet (I doesn't
looked into that now).
Example:
foobar->hw->phy->cca.mode = NL802154_CCA_ENERGY_CARRIER;
btw:
We have also there a lack of support because this describes energy
above threshold. Currently we have not implemented to get this threshold
from the phy. (We also need support for that, in case of at86rf230 the
default value is used).
- Alex
next prev parent reply other threads:[~2015-03-20 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 7:22 [PATCH bluetooth-next 1/3] ieee802154: add set transmit power support Varka Bhadram
2015-03-20 7:22 ` [PATCH bluetooth-next 2/3] cc2520: " Varka Bhadram
2015-03-20 9:19 ` Stefan Schmidt
2015-03-20 16:03 ` Alexander Aring
2015-03-20 15:30 ` Alexander Aring
2015-03-23 3:34 ` Varka Bhadram
2015-03-20 7:22 ` [PATCH bluetooth-next 3/3] cc2520: fix in updated register settings Varka Bhadram
2015-03-20 15:38 ` Alexander Aring [this message]
2015-03-20 15:28 ` [PATCH bluetooth-next 1/3] ieee802154: add set transmit power support Alexander Aring
2015-03-23 3:33 ` Varka Bhadram
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=20150320153800.GC3952@omega \
--to=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=varkab@cdac.in \
--cc=varkabhadram@gmail.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.