All of lore.kernel.org
 help / color / mirror / Atom feed
From: Varka Bhadram <varkabhadram@gmail.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org, 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 15:07:23 +0530	[thread overview]
Message-ID: <55264853.7060404@gmail.com> (raw)
In-Reply-To: <20150409092818.GC1261@omega>

On 04/09/2015 02:58 PM, Alexander Aring wrote:
> 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 <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.
>>
> 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

I think its not going to work out. But i am worrying about how the driver user
will know the power levels available..?

How mac80211 is managing this issue..?

-- 
Varka Bhadram


  reply	other threads:[~2015-04-09  9:37 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 ` [RFC bluetooth-next 0/4] ieee802154: add support for phy capabilities Varka Bhadram
2015-04-09  9:28   ` Alexander Aring
2015-04-09  9:37     ` Varka Bhadram [this message]
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=55264853.7060404@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 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.