From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Stefan Schmidt <stefan@osg.samsung.com>
Cc: linux-wpan@vger.kernel.org,
Alexander Aring <alex.aring@gmail.com>,
Stefan Schmidt <s.schmidt@samsung.com>
Subject: Re: [PATCH bluetooth-next 2/3] ieee802154/atusb: Mark driver as AACK enabled in hardware.
Date: Mon, 25 May 2015 10:41:33 +0300 [thread overview]
Message-ID: <20150525074133.GH11340@wantstofly.org> (raw)
In-Reply-To: <1432219897-29528-3-git-send-email-stefan@osg.samsung.com>
On Thu, May 21, 2015 at 04:51:36PM +0200, Stefan Schmidt wrote:
> Since firmware version 0.2 we use AACK handling directly in the firmware.
> Inform the stack that the hardware supports and uses it.
>
> Signed-off-by: Stefan Schmidt <stefan@osg.samsung.com>
> ---
> drivers/net/ieee802154/atusb.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ieee802154/atusb.c b/drivers/net/ieee802154/atusb.c
> index 9d07dd7..eef1d8a 100644
> --- a/drivers/net/ieee802154/atusb.c
> +++ b/drivers/net/ieee802154/atusb.c
> @@ -568,7 +568,8 @@ static int atusb_probe(struct usb_interface *interface,
> goto fail;
>
> hw->parent = &usb_dev->dev;
> - hw->flags = IEEE802154_HW_TX_OMIT_CKSUM | IEEE802154_HW_AFILT;
> + hw->flags = IEEE802154_HW_TX_OMIT_CKSUM | IEEE802154_HW_AFILT |
> + IEEE802154_HW_AACK;
>
> hw->phy->current_page = 0;
> hw->phy->current_channel = 11; /* reset default */
I'm wondering about this patch...
The IEEE802154_HW_AACK flag is defined in the core:
include/net/mac802154.h:
/* Indicates that receiver will autorespond with ACK frames. */
#define IEEE802154_HW_AACK 0x00000002
And is set by various drivers:
drivers/net/ieee802154/at86rf230.c: lp->hw->flags = IEEE802154_HW_TX_OMIT_CKSUM | IEEE802154_HW_AACK |
drivers/net/ieee802154/atusb.c: IEEE802154_HW_AACK;
drivers/net/ieee802154/cc2520.c: priv->hw->flags = IEEE802154_HW_OMIT_CKSUM | IEEE802154_HW_AACK |
drivers/net/ieee802154/mrf24j40.c: devrec->hw->flags = IEEE802154_HW_OMIT_CKSUM | IEEE802154_HW_AACK |
But there's no code anywhere in the tree that tests for this flag, and
if I think about it for a bit, I'm not sure what the core code could do
with this information, as I don't think it's feasible to generate ACKs
in software if the hardware doesn't support auto-ACKing? (Is hardware
that doesn't support this useful or usable at all? Maybe just remove
the flag altogether?)
next prev parent reply other threads:[~2015-05-25 7:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 14:51 [PATCH bluetooth-next 0/3] ATUSB driver updates Stefan Schmidt
2015-05-21 14:51 ` [PATCH bluetooth-next 1/3] ieee802154/atusb: Warn about outdated device firmware Stefan Schmidt
2015-05-21 14:51 ` [PATCH bluetooth-next 2/3] ieee802154/atusb: Mark driver as AACK enabled in hardware Stefan Schmidt
2015-05-25 7:41 ` Lennert Buytenhek [this message]
2015-05-26 8:56 ` Alexander Aring
2015-05-27 12:45 ` Lennert Buytenhek
2015-05-27 13:46 ` Alexander Aring
2015-05-27 16:12 ` Alexander Aring
2015-05-28 10:36 ` Lennert Buytenhek
2015-05-28 11:30 ` Alexander Aring
2015-05-28 10:29 ` Lennert Buytenhek
2015-05-28 11:25 ` Alexander Aring
2015-05-21 14:51 ` [PATCH bluetooth-next 3/3] ieee802154/atusb: Set default ed level to 0xbe like the rest of these drivers Stefan Schmidt
2015-05-21 15:36 ` [PATCH bluetooth-next 0/3] ATUSB driver updates Alexander Aring
2015-05-21 15:55 ` 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=20150525074133.GH11340@wantstofly.org \
--to=buytenh@wantstofly.org \
--cc=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