From: Varka Bhadram <varkabhadram@gmail.com>
To: Alexander Aring <alex.aring@gmail.com>, linux-wpan@vger.kernel.org
Cc: kernel@pengutronix.de,
Phoebe Buckheister <phoebe.buckheister@itwm.fraunhofer.de>
Subject: Re: [RFC bluetooth-next 0/4] ieee802154: add support for phy capabilities
Date: Thu, 09 Apr 2015 12:02:10 +0530 [thread overview]
Message-ID: <55261CEA.9080503@gmail.com> (raw)
In-Reply-To: <1428491912-14027-1-git-send-email-alex.aring@gmail.com>
On 04/08/2015 04:48 PM, Alexander Aring wrote:
> Hi,
>
> this patches introduce a mechanism to get phy capabilities. We simple add
> some additional pib values like "channels_supported" information. These
> information also includes mib values which are phy dependent like frame_retries
> or csma_backoffs, this is necessary because the phy doing a little bit mac
> stuff. We simple extend the pib according these phy dependent mac values.
>
> These capabilities are by default full 802.15.4 complaint, if some transceiver
> supports less functionality only then these values need to be overwritten inside
> the driver-layer.
>
> Fruthermore we also add functionality to dump these values via
> NL802154_CMD_GET_WPAN_PHY.
>
> - Alex
>
> Cc: Phoebe Buckheister <phoebe.buckheister@itwm.fraunhofer.de>
> Cc: Varka Bhadram <varkabhadram@gmail.com>
>
> Alexander Aring (4):
> ieee802154: introduce wpan_phy_supported struct
> ieee802154: move channels supported out of softmac
> ieee802154: add several phy supported handling
> at86rf230: set cca_modes supported flags
>
> drivers/net/ieee802154/at86rf230.c | 14 ++++++++++----
> drivers/net/ieee802154/cc2520.c | 2 +-
> drivers/net/ieee802154/fakelb.c | 30 +++++++++++++++---------------
> drivers/net/ieee802154/mrf24j40.c | 2 +-
> include/net/cfg802154.h | 11 ++++++++++-
> net/ieee802154/nl-phy.c | 4 ++--
> net/ieee802154/nl802154.c | 29 ++++++++++++++++++++++-------
> net/mac802154/cfg.c | 4 ----
> net/mac802154/main.c | 10 ++++++++++
> 9 files changed, 71 insertions(+), 35 deletions(-)
>
And also we need to look into expose available power level (supported by transeiver)
to the user space by iwpan. Then user can configure the particular power level.
If not user don't know the power levels that the transceiver support.
--
Thanks
Varka Bhadram
next prev parent reply other threads:[~2015-04-09 6:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 11:18 [RFC bluetooth-next 0/4] ieee802154: add support for phy capabilities Alexander Aring
2015-04-08 11:18 ` [RFC bluetooth-next 1/4] ieee802154: introduce wpan_phy_supported struct Alexander Aring
2015-04-09 6:17 ` Varka Bhadram
2015-04-08 11:18 ` [RFC bluetooth-next 2/4] ieee802154: move channels supported out of softmac Alexander Aring
2015-04-08 11:18 ` [RFC bluetooth-next 3/4] ieee802154: add several phy supported handling Alexander Aring
2015-04-08 14:16 ` Alexander Aring
[not found] ` <55261AB2.6050500@gmail.com>
2015-04-09 10:14 ` Alexander Aring
2015-04-08 11:18 ` [RFC bluetooth-next 4/4] at86rf230: set cca_modes supported flags Alexander Aring
2015-04-09 6:32 ` Varka Bhadram [this message]
2015-04-09 9:28 ` [RFC bluetooth-next 0/4] ieee802154: add support for phy capabilities Alexander Aring
2015-04-09 9:37 ` Varka Bhadram
2015-04-09 11:37 ` Alexander Aring
2015-04-09 12:33 ` Alexander Aring
2015-04-10 4:01 ` Varka Bhadram
2015-04-10 8:35 ` Alexander Aring
2015-04-11 12:04 ` Guido Günther
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=55261CEA.9080503@gmail.com \
--to=varkabhadram@gmail.com \
--cc=alex.aring@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-wpan@vger.kernel.org \
--cc=phoebe.buckheister@itwm.fraunhofer.de \
/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