From: Stefan Schmidt <stefan@osg.samsung.com>
To: Alexander Aring <aar@pengutronix.de>, linux-wpan@vger.kernel.org
Subject: Re: [PATCH bluetooth-next 1/4] ieee802154: atusb: implement .set_csma_params ops callback
Date: Thu, 21 Apr 2016 12:00:59 +0200 [thread overview]
Message-ID: <5718A4DB.3010300@osg.samsung.com> (raw)
In-Reply-To: <b02d54d3-7f09-e946-6dbd-316f697fc422@pengutronix.de>
Hello.
On 20/04/16 20:55, Alexander Aring wrote:
> Hi,
>
> On 04/19/2016 04:28 PM, Stefan Schmidt wrote:
>> Catching up with the stack here and implement CSMA parameter setting.
>>
>> Signed-off-by: Stefan Schmidt <stefan@osg.samsung.com>
> all patches are fine. I want to remember this settings have no effects
> until atusb has TX_ARET support and drops basic operation mode.
>
> But I am sure you already known that and this will part of next firmware
> version.
Yes, thats what I'm working on right now.
> Also please care of ed-levels if they are the same on at86rf230, don't
> known yet. There is some calculation with rssi_base_val parameter which
> is on 2.4 Ghz always -91.
I will have a look at the 230 ed level table and see if anything special
is needed for it when running atusb with the rzusb dongle.
regards
Stefan Schmidt
next prev parent reply other threads:[~2016-04-21 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 14:28 [PATCH bluetooth-next 1/4] ieee802154: atusb: implement .set_csma_params ops callback Stefan Schmidt
2016-04-19 14:28 ` [PATCH bluetooth-next 2/4] ieee802154: atusb: implement .set_cca_ed_level " Stefan Schmidt
2016-04-19 14:28 ` [PATCH bluetooth-next 3/4] ieee802154: atusb: implement .set_cca_mode " Stefan Schmidt
2016-04-19 14:28 ` [PATCH bluetooth-next 4/4] ieee802154: atusb: update my copyright years for this driver Stefan Schmidt
2016-04-20 18:55 ` [PATCH bluetooth-next 1/4] ieee802154: atusb: implement .set_csma_params ops callback Alexander Aring
2016-04-20 22:22 ` Marcel Holtmann
2016-04-21 10:00 ` Stefan Schmidt [this message]
2016-04-21 18:49 ` Stefan Schmidt
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=5718A4DB.3010300@osg.samsung.com \
--to=stefan@osg.samsung.com \
--cc=aar@pengutronix.de \
--cc=linux-wpan@vger.kernel.org \
/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