From: Johan Hedberg <johan.hedberg@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 05/12 v3] Bluetooth: Switch from hdev->cmd_q to using transactions
Date: Mon, 18 Feb 2013 09:48:25 +0200 [thread overview]
Message-ID: <20130218074825.GC17232@x220> (raw)
In-Reply-To: <1361053337.1583.7.camel@aeonflux>
Hi Marcel,
On Sat, Feb 16, 2013, Marcel Holtmann wrote:
> > static void hci_init_req(struct hci_dev *hdev, unsigned long opt)
> > {
> > + struct hci_transaction *transaction;
> > struct sk_buff *skb;
> >
> > BT_DBG("%s %ld", hdev->name, opt);
> >
> > /* Driver initialization */
> >
> > + if (hci_start_transaction(hdev) < 0)
> > + return;
> > +
> > + hci_transaction_lock(hdev);
> > +
> > + transaction = hdev->build_transaction;
> > +
> > /* Special commands */
> > while ((skb = skb_dequeue(&hdev->driver_init))) {
> > bt_cb(skb)->pkt_type = HCI_COMMAND_PKT;
> > skb->dev = (void *) hdev;
> > -
> > - skb_queue_tail(&hdev->cmd_q, skb);
> > - queue_work(hdev->workqueue, &hdev->cmd_work);
> > + skb_queue_tail(&transaction->cmd_q, skb);
> > }
> > skb_queue_purge(&hdev->driver_init);
>
> if we have to touch this one, then please look at my hdev->setup()
> patches I send a while back. We should get these merged so that drivers
> can use a transaction within the driver and remove the driver_init queue
> actually.
Alright. I'll look into it.
Johan
next prev parent reply other threads:[~2013-02-18 7:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 9:51 [PATCH 00/12 v3] Bluetooth: Asynchronous HCI transaction API Johan Hedberg
2013-02-15 9:51 ` [PATCH 01/12 v3] Bluetooth: Add initial hooks for HCI transaction support Johan Hedberg
2013-02-15 9:51 ` [PATCH 02/12 v3] Bluetooth: Add basic start/complete HCI transaction functions Johan Hedberg
2013-02-16 22:17 ` Marcel Holtmann
2013-02-18 7:43 ` Johan Hedberg
2013-02-18 12:47 ` Marcel Holtmann
2013-02-15 9:51 ` [PATCH 03/12 v3] Bluetooth: Add hci_transaction_cmd_complete function Johan Hedberg
2013-02-16 22:19 ` Marcel Holtmann
2013-02-18 7:46 ` Johan Hedberg
2013-02-15 9:51 ` [PATCH 04/12 v3] Bluetooth: Add hci_transaction_from_skb function Johan Hedberg
2013-02-15 9:51 ` [PATCH 05/12 v3] Bluetooth: Switch from hdev->cmd_q to using transactions Johan Hedberg
2013-02-16 22:22 ` Marcel Holtmann
2013-02-18 7:48 ` Johan Hedberg [this message]
2013-02-15 9:51 ` [PATCH 06/12 v3] Bluetooth: Remove unused hdev->cmd_q HCI command queue Johan Hedberg
2013-02-15 9:51 ` [PATCH 07/12 v3] Bluetooth: Fix mgmt powered indication by using a HCI transaction Johan Hedberg
2013-02-19 19:36 ` Andre Guedes
2013-02-15 9:51 ` [PATCH 08/12 v3] Bluetooth: Enable HCI transaction support cmd_status 0 Johan Hedberg
2013-02-15 9:51 ` [PATCH 09/12 v3] Bluetooth: Add HCI init sequence support for HCI transactions Johan Hedberg
2013-02-15 9:51 ` [PATCH 10/12 v3] Bluetooth: Convert hci_request to use " Johan Hedberg
2013-02-15 9:51 ` [PATCH 11/12 v3] Bluetooth: Remove unused hdev->init_last_cmd Johan Hedberg
2013-02-15 9:52 ` [PATCH 12/12 v3] Bluetooth: Remove empty HCI event handlers Johan Hedberg
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=20130218074825.GC17232@x220 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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).