Linux IEEE 802.15.4 and 6LoWPAN development
 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, Stefan Schmidt <s.schmidt@samsung.com>
Subject: Re: [PATCHv2 bluetooth-next 3/4] ieee802154/atusb: Add .set_promiscuous_mode driver operation
Date: Fri, 29 May 2015 11:17:17 +0200	[thread overview]
Message-ID: <20150529091713.GC3709@omega> (raw)
In-Reply-To: <1432889488-28420-4-git-send-email-stefan@osg.samsung.com>

Hi Stefan,

On Fri, May 29, 2015 at 10:51:27AM +0200, Stefan Schmidt wrote:
> From: Stefan Schmidt <s.schmidt@samsung.com>
> 
> Allow monitor mode operation with disabled AACK in hardware.
> 
> Signed-off-by: Stefan Schmidt <stefan@osg.samsung.com>
> ---
>  drivers/net/ieee802154/atusb.c | 30 +++++++++++++++++++++++++++++-
>  1 file changed, 29 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/net/ieee802154/atusb.c b/drivers/net/ieee802154/atusb.c
> index 9805ebe..3d25678 100644
> --- a/drivers/net/ieee802154/atusb.c
> +++ b/drivers/net/ieee802154/atusb.c
> @@ -473,6 +473,33 @@ atusb_set_txpower(struct ieee802154_hw *hw, s32 mbm)
>  	return -EINVAL;
>  }
>  
> +static int
> +atusb_set_promiscuous_mode(struct ieee802154_hw *hw, const bool on)
> +{
> +	struct atusb *atusb = hw->priv;
> +	int ret;
> +
> +	if (on) {
> +		ret = atusb_write_subreg(atusb, SR_AACK_DIS_ACK, 1);
> +		if (ret < 0)
> +			return ret;
> +
> +		ret = atusb_write_subreg(atusb, SR_AACK_PROM_MODE, 1);
> +		if (ret < 0)
> +			return ret;
> +	} else {
> +		ret = atusb_write_subreg(atusb, SR_AACK_PROM_MODE, 0);
> +		if (ret < 0)
> +			return ret;
> +
> +		ret = atusb_write_subreg(atusb, SR_AACK_DIS_ACK, 0);
> +		if (ret < 0)
> +			return ret;
> +	}
> +
> +	return 0;
> +}
> +

In case of rzusb which have an at86rf230 it doesn't support these
registers. There is no support for promiscuous mode. It's then a
broken behaviour when somebody sets this in rzusb.

Anyway rzusb isn't currently supported and I just want to leave a note
here. It's fine for me. Something for later to fix it in driver or
firmware handling.

- Alex

  reply	other threads:[~2015-05-29  9:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29  8:51 [PATCHv2 bluetooth-next 0/4] Atusb driver improvements Stefan Schmidt
2015-05-29  8:51 ` [PATCHv2 bluetooth-next 1/4] ieee802154/atusb: Add function for partial register writes Stefan Schmidt
2015-05-29  8:51 ` [PATCHv2 bluetooth-next 2/4] ieee802154/atusb: Add .set_txpower operation to the driver Stefan Schmidt
2015-05-29  9:19   ` Alexander Aring
2015-05-29  9:27     ` Stefan Schmidt
2015-05-29  8:51 ` [PATCHv2 bluetooth-next 3/4] ieee802154/atusb: Add .set_promiscuous_mode driver operation Stefan Schmidt
2015-05-29  9:17   ` Alexander Aring [this message]
2015-05-29  8:51 ` [PATCHv2 bluetooth-next 4/4] MAINTAINERS: Add myself as maintainer for the atusb driver Stefan Schmidt
2015-05-29  9:03 ` [PATCHv2 bluetooth-next 0/4] Atusb driver improvements Varka Bhadram
2015-05-29  9:39 ` Alexander Aring
2015-05-29 13:41 ` Marcel Holtmann

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=20150529091713.GC3709@omega \
    --to=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=s.schmidt@samsung.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox