All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Varka Bhadram <varkabhadram@gmail.com>
Cc: linux-wpan@vger.kernel.org, Varka Bhadram <varkab@cdac.in>
Subject: Re: [PATCH bluetooth-next] nl802154: export supported commands
Date: Wed, 3 Jun 2015 08:49:54 +0200	[thread overview]
Message-ID: <20150603064950.GB731@omega> (raw)
In-Reply-To: <1433304841-12734-1-git-send-email-varkab@cdac.in>

Hi,

On Wed, Jun 03, 2015 at 09:44:01AM +0530, Varka Bhadram wrote:
> This patch will export the supported commands by the devices
> to the user. This is required because user should know supported
> commands by the IEEE-802.15.4 devices. Drivers that are there in
> the mainline are not supporting all the functionalities that the
> core is providing to us.
> 

I think this is not the reason why this was implemented. You check here
cfg802154_ops which ends in mac802154 (SoftMAC) OR _possible_ HardMAC drivers.

If you want to make sure that a driver implement it _and_ really sure
you need to check on ieee802154_ops.

I suppose the real reason why wireless has this implementation, is
because to check if HardMAC drivers can support a specific command.
This is because every HardMAC driver should implement then the full
cfg802154_ops callback structure. It's simple wrong here to say "to
check if the driver support the functionalities".

You skip the mac802154 layer here, these calls are direct driver-layer
calls in case of HardMAC driver only.


Currently that's why I think such feature has _at_ _the_ _moment_ no
really big use case, because we don't have any HardMAC driver currently.
Anyway this prepares to handle HardMAC drivers. After fixing the commit
message you can add a:

Acked-by: Alexander Aring <alex.aring@gmail.com>

> Signed-off-by: Varka Bhadram <varkab@cdac.in>
> ---
>  include/net/nl802154.h    |    2 ++
>  net/ieee802154/nl802154.c |   36 ++++++++++++++++++++++++++++++++++++
>  2 files changed, 38 insertions(+)
> 
> diff --git a/include/net/nl802154.h b/include/net/nl802154.h
> index 0badebd..6fc231e 100644
> --- a/include/net/nl802154.h
> +++ b/include/net/nl802154.h
> @@ -102,6 +102,8 @@ enum nl802154_attrs {
>  
>  	NL802154_ATTR_WPAN_PHY_CAPS,
>  
> +	NL802154_ATTR_SUPPORTED_COMMANDS,
> +
>  	/* add attributes here, update the policy in nl802154.c */
>  
>  	__NL802154_ATTR_AFTER_LAST,
> diff --git a/net/ieee802154/nl802154.c b/net/ieee802154/nl802154.c
> index 7dbb1f4..310a519 100644
> --- a/net/ieee802154/nl802154.c
> +++ b/net/ieee802154/nl802154.c
> @@ -372,7 +372,9 @@ static int nl802154_send_wpan_phy(struct cfg802154_registered_device *rdev,
>  				  struct sk_buff *msg, u32 portid, u32 seq,
>  				  int flags)
>  {
> +	struct nlattr *nl_cmds;
>  	void *hdr;
> +	int i;
>  
>  	hdr = nl802154hdr_put(msg, portid, seq, flags, cmd);
>  	if (!hdr)
> @@ -431,6 +433,40 @@ static int nl802154_send_wpan_phy(struct cfg802154_registered_device *rdev,
>  	if (nl802154_put_capabilities(msg, rdev))
>  		goto nla_put_failure;
>  
> +	nl_cmds = nla_nest_start(msg, NL802154_ATTR_SUPPORTED_COMMANDS);
> +	if (!nl_cmds)
> +		goto nla_put_failure;
> +
> +	i = 0;
> +#define CMD(op, n)							\
> +	do {								\
> +		if (rdev->ops->op) {					\
> +			i++;						\
> +			if (nla_put_u32(msg, i, NL802154_CMD_ ## n))	\
> +				goto nla_put_failure;			\
> +		}							\
> +	} while (0)
> +
> +	CMD(add_virtual_intf, NEW_INTERFACE);
> +	CMD(del_virtual_intf, DEL_INTERFACE);
> +	CMD(set_channel, SET_CHANNEL);
> +	CMD(set_pan_id, SET_PAN_ID);
> +	CMD(set_short_addr, SET_SHORT_ADDR);
> +	CMD(set_backoff_exponent, SET_BACKOFF_EXPONENT);
> +	CMD(set_max_csma_backoffs, SET_MAX_CSMA_BACKOFFS);
> +	CMD(set_max_frame_retries, SET_MAX_FRAME_RETRIES);
> +
> +	if (rdev->wpan_phy.flags & WPAN_PHY_FLAG_TXPOWER)
> +		CMD(set_tx_power, SET_TX_POWER);
> +
> +	if (rdev->wpan_phy.flags & WPAN_PHY_FLAG_CCA_ED_LEVEL)
> +		CMD(set_cca_ed_level, SET_CCA_ED_LEVEL);
> +
> +	if (rdev->wpan_phy.flags & WPAN_PHY_FLAG_CCA_MODE)
> +		CMD(set_cca_mode, SET_CCA_MODE);
> +#undef CMD
> +	nla_nest_end(msg, nl_cmds);
> +
>  finish:
>  	genlmsg_end(msg, hdr);
>  	return 0;
> -- 
> 1.7.9.5
> 

  reply	other threads:[~2015-06-03  6:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03  4:14 [PATCH bluetooth-next] nl802154: export supported commands Varka Bhadram
2015-06-03  6:49 ` Alexander Aring [this message]
2015-06-03  7:13   ` Varka Bhadram
2015-06-03  7:48     ` Alexander Aring
2015-06-04  7:30 ` Alexander Aring
  -- strict thread matches above, loose matches on Subject: below --
2015-06-03  4:09 Varka Bhadram
2015-06-03  4:12 ` Varka Bhadram

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=20150603064950.GB731@omega \
    --to=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=varkab@cdac.in \
    --cc=varkabhadram@gmail.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.