From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Aarthi Thiruvengadam <athiruve@qca.qualcomm.com>
Cc: <ath6kl-devel@qualcomm.com>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath6kl: support for P2P mgmt operations on station interface
Date: Wed, 14 Dec 2011 20:44:16 +0200 [thread overview]
Message-ID: <4EE8EE80.8090008@qca.qualcomm.com> (raw)
In-Reply-To: <1323811932-5724-1-git-send-email-aarthi.thiruvengadam@qca.qualcomm.com>
On 12/13/2011 11:32 PM, Aarthi Thiruvengadam wrote:
> This patch enables support for doing P2P management operations like device
> discovery on top of a station interface. After group formation, the station
> interface will become a P2P GO/client interface as the case may be.
>
> This feature requires modifications to a couple of existing WMI structures and
> therefore new command ids and structures have been defined in order to be
> compatible with older firmware versions and other chips. The exception here is
> the wmi_connect_cmd. Adding a new field to the end of the structure will not
> cause any issues with previous firmware versions since firmware only checks for
> minimum length of the command. The other structures are of variable length,
> hence it was not possible to add new fields to the end.
>
> The new command ids have to be added to the end of enum wmi_cmd_id, so it has
> updated to match the firmware.
>
> The driver will support both the 'old' and the 'new' commands for a while by
> checking the firmware capabilities.
>
> Signed-off-by: Aarthi Thiruvengadam <athiruve@qca.qualcomm.com>
Thanks, applied.
Kalle
prev parent reply other threads:[~2011-12-14 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 21:32 [PATCH] ath6kl: support for P2P mgmt operations on station interface Aarthi Thiruvengadam
2011-12-14 18:44 ` Kalle Valo [this message]
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=4EE8EE80.8090008@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=athiruve@qca.qualcomm.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).