netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Phoebe Buckheister <phoebe.buckheister@itwm.fraunhofer.de>,
	netdev@vger.kernel.org
Cc: linux-zigbee-devel@lists.sourceforge.net, davem@davemloft.net
Subject: Re: [PATCH net-next 04/10] ieee802154: support 100kbps QPSK/EU in at86rf230
Date: Wed, 12 Feb 2014 23:01:11 +0300	[thread overview]
Message-ID: <52FBD307.9080909@cogentembedded.com> (raw)
In-Reply-To: <1392223034-19955-5-git-send-email-phoebe.buckheister@itwm.fraunhofer.de>

Hello.

On 02/12/2014 07:37 PM, Phoebe Buckheister wrote:

> The standard assigns channel 0 on page 2 to be 100kbps QPSK in the
> 868.3MHz band. Add support to the at86rf230 driver for this channel and
> page, at the moment predicated only for the RF212 chip.

> Per the datasheet, configurations for page 0, channels 0 to 10 and page
> 2, channels 0 to 10 differ only in the BPSK_QPSK bit. Support for
> channels 1 to 10 is untested.

> Signed-off-by: Phoebe Buckheister <phoebe.buckheister@itwm.fraunhofer.de>
> ---
>   drivers/net/ieee802154/at86rf230.c |   17 ++++++++++++++---
>   1 file changed, 14 insertions(+), 3 deletions(-)

> diff --git a/drivers/net/ieee802154/at86rf230.c b/drivers/net/ieee802154/at86rf230.c
> index 99bc822..f6338c4 100644
> --- a/drivers/net/ieee802154/at86rf230.c
> +++ b/drivers/net/ieee802154/at86rf230.c
[...]
> @@ -595,6 +596,14 @@ at86rf212_set_channel(struct at86rf230_local *lp, int page, int channel)
>   	if (rc < 0)
>   		return rc;
>
> +	if (page == 0)
> +		rc = at86rf230_write_subreg(lp, SR_BPSK_QPSK, 0);
> +	else
> +		rc = at86rf230_write_subreg(lp, SR_BPSK_QPSK, 1);
> +

    Don't think empty line is needed here.

> +	if (rc < 0)
> +		return rc;
> +
>   	return at86rf230_write_subreg(lp, SR_CHANNEL, channel);
>   }
>
[...]
> @@ -1067,9 +1077,10 @@ static int at86rf230_probe(struct spi_device *spi)
>
>   	spi_set_drvdata(spi, lp);
>
> -	if (is_rf212(lp))
> +	if (is_rf212(lp)) {
>   		dev->phy->channels_supported[0] = 0x00007FF;
> -	else
> +		dev->phy->channels_supported[2] = 0x00007FF;
> +	} else
>   		dev->phy->channels_supported[0] = 0x7FFF800;

    Have to use {} in both arms of the *if* statement now -- see 
Documentation/CodingStyle.

WBR, Sergei

  reply	other threads:[~2014-02-12 19:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 16:37 [PATCH net-next 0/10] ieee802154: support rf212 and extended mac features Phoebe Buckheister
2014-02-12 16:37 ` [PATCH net-next 01/10] ieee802154: add basic support for RF212 to at86rf230 driver Phoebe Buckheister
2014-02-12 16:37 ` [PATCH net-next 03/10] ieee802154: add TX power control to wpan_phy Phoebe Buckheister
     [not found] ` <1392223034-19955-1-git-send-email-phoebe.buckheister-mPn0NPGs4xGatNDF+KUbs4QuADTiUCJX@public.gmane.org>
2014-02-12 16:37   ` [PATCH net-next 02/10] ieee802154: default to AACK in at86rf230 Phoebe Buckheister
2014-02-12 16:37   ` [PATCH net-next 04/10] ieee802154: support 100kbps QPSK/EU " Phoebe Buckheister
2014-02-12 20:01     ` Sergei Shtylyov [this message]
2014-02-12 16:37   ` [PATCH net-next 05/10] ieee802154: add support for listen-before-talk in wpan_phy Phoebe Buckheister
2014-02-12 16:37   ` [PATCH net-next 06/10] ieee802154: add support for CCA mode in wpan phys Phoebe Buckheister
2014-02-12 16:37   ` [PATCH net-next 07/10] ieee802154: add support for setting CCA energy detection levels Phoebe Buckheister
2014-02-12 16:37 ` [PATCH net-next 08/10] ieee802154: ensure that first RF212 state comes from TRX_OFF Phoebe Buckheister
2014-02-12 16:37 ` [PATCH net-next 09/10] ieee802154: add netlink APIs for smartMAC configuration Phoebe Buckheister
2014-02-12 16:37 ` [PATCH net-next 10/10] ieee802154: enable smart transmitter features of RF212 Phoebe Buckheister

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=52FBD307.9080909@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=davem@davemloft.net \
    --cc=linux-zigbee-devel@lists.sourceforge.net \
    --cc=netdev@vger.kernel.org \
    --cc=phoebe.buckheister@itwm.fraunhofer.de \
    /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).