From: Johannes Berg <johannes@sipsolutions.net>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [RFCv2 1/6] mac80211: softamp: Adds Bluetooth Software AMP
Date: Mon, 07 May 2012 13:59:31 +0200 [thread overview]
Message-ID: <1336391971.4325.25.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20120507115608.GD19002@aemeltch-MOBL1>
On Mon, 2012-05-07 at 14:56 +0300, Andrei Emeltchenko wrote:
> Hi Johannes,
>
> On Mon, May 07, 2012 at 01:41:19PM +0200, Johannes Berg wrote:
> > On Tue, 2012-04-24 at 16:17 +0300, Andrei Emeltchenko wrote:
> >
> > > --- a/include/linux/nl80211.h
> > > +++ b/include/linux/nl80211.h
> > > @@ -1546,6 +1546,7 @@ enum nl80211_iftype {
> > > NL80211_IFTYPE_MESH_POINT,
> > > NL80211_IFTYPE_P2P_CLIENT,
> > > NL80211_IFTYPE_P2P_GO,
> > > + NL80211_IFTYPE_BLUETOOTH_SOFTAMP,
> >
> > That should probably be a separate patch also updating cfg80211 (and
> > maybe mac80211) where needed (at least to suppress the warnings you
> > saw). Also documentation is needed.
> >
> > > @@ -211,6 +212,7 @@ static int ieee80211_do_open(struct net_device *dev, bool coming_up)
> > > case NL80211_IFTYPE_STATION:
> > > case NL80211_IFTYPE_MONITOR:
> > > case NL80211_IFTYPE_ADHOC:
> > > + case NL80211_IFTYPE_BLUETOOTH_SOFTAMP:
> > > /* no special treatment */
> > > break;
> >
> > You should never be able to come here with this interface type -- maybe
> > make it a warning or something.
> >
> > > +static int vamp_send_frame(struct sk_buff *skb)
> > > +{
> > > + struct hci_dev *hdev = (struct hci_dev *) skb->dev;
> > > + struct vamp_data *data;
> > > +
> > > + BT_DBG("%s", hdev->name);
> > > +
> > > + if (!hdev) {
> > > + BT_ERR("Frame for unknown HCI device (hdev=NULL)");
> > > + return -ENODEV;
> > > + }
> > > +
> > > + if (!test_bit(HCI_RUNNING, &hdev->flags))
> > > + return -EBUSY;
> > > +
> > > + data = hci_get_drvdata(hdev);
> > > +
> > > + skb_queue_tail(&data->txq, skb);
> > > +
> > > + schedule_work(&data->work);
> >
> > I don't understand the need for the asynchronous handling.
>
> This is standard way for hci dev. Can be changed so that skb is handled
> right here.
"standard" doesn't explain why it's needed though, and I don't think it
is needed here.
johannes
next prev parent reply other threads:[~2012-05-07 11:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 13:17 [RFCv2 0/6] Draft Software/Virtual AMP80211 Andrei Emeltchenko
2012-04-24 13:17 ` [RFCv2 1/6] mac80211: softamp: Adds Bluetooth Software AMP Andrei Emeltchenko
2012-05-07 11:41 ` Johannes Berg
2012-05-07 11:56 ` Andrei Emeltchenko
2012-05-07 11:59 ` Johannes Berg [this message]
2012-04-24 13:17 ` [RFCv2 2/6] mac80211: softamp: Adds build config option Andrei Emeltchenko
2012-04-24 13:17 ` [RFCv2 3/6] hwsim: Adds support for BT SOFTAMP for testing Andrei Emeltchenko
2012-04-24 13:17 ` [RFCv2 4/6] mac80211: softamp: Handle assoc request Andrei Emeltchenko
2012-05-07 11:42 ` Johannes Berg
2012-04-24 13:17 ` [RFCv2 5/6] mac80211: softamp: Netlink interface to softamp Andrei Emeltchenko
2012-05-07 11:42 ` Johannes Berg
2012-04-24 13:17 ` [RFCv2 6/6] mac80211: softamp: Handle data traffic Andrei Emeltchenko
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=1336391971.4325.25.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Andrei.Emeltchenko.news@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--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).