All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xue Liu <liuxuenetmail@gmail.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: Stefan Schmidt <stefan@osg.samsung.com>,
	linux-wpan - ML <linux-wpan@vger.kernel.org>
Subject: Re: [PATCHv2 3/3] ieee802154: Add MCR20A IEEE 802.15.4 device driver
Date: Tue, 20 Feb 2018 11:42:38 +0100	[thread overview]
Message-ID: <CAJuUDwu+TYo18jQ1E5nT63+6wL+bONz74q0tasEGdKy_L-m+Qw@mail.gmail.com> (raw)
In-Reply-To: <CAB_54W7GvgkCqd1HoGs3RrsarRHfyQ346tYbbWbDPjkUEd46-A@mail.gmail.com>

Hello,


On 20 February 2018 at 04:44, Alexander Aring <alex.aring@gmail.com> wrote:
> Hi,
>
> 2018-02-19 18:49 GMT-05:00 Xue Liu <liuxuenetmail@gmail.com>:
>> Hello.
>>
>> I have one more question about ieee802154_ops.ed function. How to test
>> this function ? Thanks
>
> This function is/was never used by the subsystem. It has historical
> reason _why_ this function is still there... The original repository
> had "something" half working of MLME-SCAN (In my opinion). They got
> this callback there but then nothing more...
>
> What you could introduce is a netlink notifier command which reports
> by reaching some threshold, e.g.
>
> iwpan phy0 get edthresh $VAL -> blocks until ed reached above thresh,
> which should happen when transmit is going on on your channel...
>
> Or just a get command?
>
> There exists also various way to receive ED values, we should offer
> them as well than just trigger it from outside, e.g. after each frame
> rx... this need to be collected at a main point.
>
> - Alex

Thanks for all the explanation.

Regards,

Xue Liu

  reply	other threads:[~2018-02-20 10:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 10:51 [PATCHv2 0/3] ieee802154: Add support for NXP MCR20A Xue Liu
2018-02-19 10:51 ` [PATCHv2 1/3] ieee802154: Add device tree documentation for MCR20A Xue Liu
2018-02-19 10:51 ` [PATCHv2 2/3] ieee802154: Add entry in MAINTAINTERS for MCR20a driver Xue Liu
2018-02-19 10:51 ` [PATCHv2 3/3] ieee802154: Add MCR20A IEEE 802.15.4 device driver Xue Liu
2018-02-19 16:31   ` Stefan Schmidt
2018-02-19 21:40     ` Xue Liu
2018-02-19 22:37       ` Stefan Schmidt
2018-02-19 23:49         ` Xue Liu
2018-02-20  3:44           ` Alexander Aring
2018-02-20 10:42             ` Xue Liu [this message]
2018-02-19 23:59         ` Xue Liu
2018-02-20  9:27           ` Stefan Schmidt
2018-02-20 10:45             ` Xue Liu
2018-02-19 17:29   ` Michael Richardson
2018-02-19 21:42     ` Xue Liu
2018-02-20  3:37     ` Alexander Aring
2018-02-20 10:53       ` Xue Liu

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=CAJuUDwu+TYo18jQ1E5nT63+6wL+bONz74q0tasEGdKy_L-m+Qw@mail.gmail.com \
    --to=liuxuenetmail@gmail.com \
    --cc=alex.aring@gmail.com \
    --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 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.