Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFCv0] Bluetooth: General HCI callback implementation
Date: Wed, 14 Dec 2011 23:20:23 +0100	[thread overview]
Message-ID: <1323901223.1965.70.camel@aeonflux> (raw)
In-Reply-To: <1323436248-3736-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>

Hi Andrei,

> Add general HCI callback implementation. Can be used for executing
> HCI commands from A2MP protocol.
> ---
>  include/net/bluetooth/hci_core.h |   14 +++++++++++
>  net/bluetooth/hci_core.c         |   47 ++++++++++++++++++++++++++++++++++++++
>  net/bluetooth/hci_event.c        |    4 +++
>  3 files changed, 65 insertions(+), 0 deletions(-)
> 
> diff --git a/include/net/bluetooth/hci_core.h b/include/net/bluetooth/hci_core.h
> index cc5481d..e473cd2 100644
> --- a/include/net/bluetooth/hci_core.h
> +++ b/include/net/bluetooth/hci_core.h
> @@ -121,6 +121,15 @@ struct adv_entry {
>  	u8 bdaddr_type;
>  };
>  
> +struct hci_dev;
> +
> +struct cb_cmd {
> +	struct list_head list;
> +	u16 opcode;
> +	void *opt;
> +	void (*cb)(struct hci_dev *hdev, void *opt);
> +};
> +

so I am actually thinking that we might just update hci_request into a
bit more flexible schema.

Gustavo is working on moving everything into a process context, so we
can actually sleep. And we could just make a simple premise to only
allow one request at a time. That would also then allow us to utilize
hci_request. We just need a clean way to report back the result.

Regards

Marcel



  parent reply	other threads:[~2011-12-14 22:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09 13:10 [RFCv0] Bluetooth: General HCI callback implementation Emeltchenko Andrei
2011-12-10 12:47 ` Anderson Lizardo
2011-12-12  9:15   ` Emeltchenko Andrei
2011-12-14 22:20 ` Marcel Holtmann [this message]
2011-12-15  9:19   ` Emeltchenko Andrei
2011-12-15  9:40     ` Marcel Holtmann

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=1323901223.1965.70.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=Andrei.Emeltchenko.news@gmail.com \
    --cc=linux-bluetooth@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