From: Josef Filzmaier <j.filzmaier@gmx.at>
To: Stefan Schmidt <stefan@osg.samsung.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: AT86RF212 based USB-Stick (HUL)
Date: Wed, 16 Aug 2017 17:33:57 +0200 [thread overview]
Message-ID: <1551752.M6fFiAEvOh@hella-laptop> (raw)
In-Reply-To: <215b5391-2082-6061-5365-b693008c9c9d@osg.samsung.com>
Hello again :)
> Let me know how it goes.
I have made some progress regarding the busware hul stick support. I had two
major problems:
1) The atusb_xmit function is only called *once* and then never again
2) Configuring page, channel and txpower did not work.
I think that i did fix 2) successfully. (Firmware Patch: [1], Kernel Patch: [2]
(Please ignore the modified device tree)) I hopefully did not break
compatability with rzusb and atusb, could you please verify that and give some
comments on my code?
For 1) however, i still have some problems - and am seeking for some help.
The first time i try to send a frame i get roughly the following function
calling sequence (bottom up):
atusb_xmit
ieee802154_tx
ieee802154_subif_start_xmit
dev_hard_start_xmit
sch_direct_xmit
__dev_xmit_skb
__dev_queue_xmit
...
However, the second time i try to send a frame i get the following sequence:
sch_direct_xmit
__dev_xmit_skb
__dev_queue_xmit
...
The reason for this is that !netif_xmit_frozen_or_stopped(txq) (see [3]) is
false, so the dev_hard_start_xmit() function is never called.
It is returning false because the netdev_queue is in state
QUEUE_STATE_DRV_XOFF.
As far as i can tell this state change happens in the ieee802154_tx() [4]
method with the ieee802154_stop_queue(&local->hw) function call.
What could be wrong here? Do i have to call ieee802154_wake_queue() somewhere?
Or where should the netdev_queue state be reset so that the queue state is
back at 0 that new frames can be sent. Or am i missing something completely
here?
> That would be great. I will send you my address directly.
I just realized that your email with the address was in my spam folder. I will
send you one ASAP.
Regards,
Josef
[1] https://github.com/joseffilzmaier/ben-wpan/compare/busware-hul
[2] https://github.com/raspberrypi/linux/compare/
rpi-4.9.y...joseffilzmaier:atusb-busware-hul
[3] http://elixir.free-electrons.com/linux/v4.9.40/source/net/sched/
sch_generic.c#L181
[4] http://elixir.free-electrons.com/linux/v4.9.40/source/net/mac802154/
tx.c#L72
--
Josef Filzmaier
next prev parent reply other threads:[~2017-08-16 15:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 14:26 Re: AT86RF212 based USB-Stick (HUL) Josef Filzmaier
2017-08-03 15:50 ` Stefan Schmidt
2017-08-03 20:51 ` Josef Filzmaier
2017-08-03 21:09 ` Stefan Schmidt
2017-08-16 15:33 ` Josef Filzmaier [this message]
2017-08-17 8:28 ` Josef Filzmaier
2017-08-17 10:13 ` Stefan Schmidt
2017-08-17 10:10 ` Stefan Schmidt
2017-08-17 11:14 ` Josef Filzmaier
2017-08-17 11:42 ` Stefan Schmidt
2017-08-18 10:26 ` Josef Filzmaier
2017-08-18 10:33 ` Stefan Schmidt
2017-08-24 13:54 ` Stefan Schmidt
[not found] <526ff7aa-6342-4a8e-8278-0d76d897044e@email.android.com>
2017-08-29 7:30 ` Stefan Schmidt
2017-09-04 16:22 ` Josef Filzmaier
2017-09-11 11:13 ` Stefan Schmidt
2017-09-11 12:05 ` Josef Filzmaier
-- strict thread matches above, loose matches on Subject: below --
2017-08-02 16:00 Josef Filzmaier
2017-08-03 6:59 ` Stefan Schmidt
2017-08-03 13:44 ` Alexander Aring
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=1551752.M6fFiAEvOh@hella-laptop \
--to=j.filzmaier@gmx.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox