From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f171.google.com ([209.85.212.171]:33005 "EHLO mail-wi0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933311AbbDIJ2Z (ORCPT ); Thu, 9 Apr 2015 05:28:25 -0400 Received: by wiax7 with SMTP id x7so50962028wia.0 for ; Thu, 09 Apr 2015 02:28:24 -0700 (PDT) Date: Thu, 9 Apr 2015 11:28:21 +0200 From: Alexander Aring Subject: Re: [RFC bluetooth-next 0/4] ieee802154: add support for phy capabilities Message-ID: <20150409092818.GC1261@omega> References: <1428491912-14027-1-git-send-email-alex.aring@gmail.com> <55261CEA.9080503@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <55261CEA.9080503@gmail.com> Sender: linux-wpan-owner@vger.kernel.org List-ID: To: Varka Bhadram Cc: linux-wpan@vger.kernel.org, kernel@pengutronix.de, Phoebe Buckheister On Thu, Apr 09, 2015 at 12:02:10PM +0530, Varka Bhadram wrote: > 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 > > Cc: Varka Bhadram > > > > 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. > yep... I will try to add it to the next series, also for ed_level. For 700/800/900 Mhz at86rf212 it depends on which band the transceiver operates and the available tx_power settings. When I try to implement it, then I need to know the country/band laws what's the min and max tx_power db values? Does something like this exists? Is s8 as datatype really enough to support all available tx_power settings? -> (not because I also saw some floating point tx_power settings, but then we simple doesn't provide them). I will try to introduce something which supports the at86rf2xx transceiver values. We can still change the interface again later if it doesn't fit, but then everybody will hate us. :-) - Alex