linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>
To: "Frédéric Dalleau" <frederic.dalleau@linux.intel.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC 4/4] Bluetooth: Set link parameters for outgoing connections
Date: Thu, 29 Nov 2012 11:31:49 +0200	[thread overview]
Message-ID: <20121129093147.GA2574@aemeltch-MOBL1> (raw)
In-Reply-To: <1354127316-17431-5-git-send-email-frederic.dalleau@linux.intel.com>

Hi Frédéric,

On Wed, Nov 28, 2012 at 07:28:36PM +0100, Frédéric Dalleau wrote:
> In order to establish the connection, the outgoing connection must also
> request the codec. Here we need to set a bit in ACL connection flag to set up
> the correct parameters if the ACL connection is not up yet.

...

> @@ -585,7 +586,8 @@ void hci_chan_list_flush(struct hci_conn *conn);
>  struct hci_chan *hci_chan_lookup_handle(struct hci_dev *hdev, __u16 handle);
>  
>  struct hci_conn *hci_connect(struct hci_dev *hdev, int type, bdaddr_t *dst,
> -			     __u8 dst_type, __u8 sec_level, __u8 auth_type);
> +			     __u8 dst_type, __u8 sec_level,
> +			     __u8 auth_type, __u8 codec);

somehow I do not like this new parameter for hci_connect as it is only
needed for SCO.

Now I am not sure we need hci_connect super-function if it only calls
appropriate hci_connect_{sco,acl,le} based on type.

...
> @@ -552,7 +559,8 @@ static struct hci_conn *hci_connect_acl(struct hci_dev *hdev, bdaddr_t *dst,
>  }
>  
>  static struct hci_conn *hci_connect_sco(struct hci_dev *hdev, int type,
> -				bdaddr_t *dst, u8 sec_level, u8 auth_type)
> +					bdaddr_t *dst, u8 sec_level,
> +					u8 auth_type, u8 codec)

what about directly calling hci_connect_sco with the parameter?

...

Best regards 
Andrei Emeltchenko 


  reply	other threads:[~2012-11-29  9:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28 18:28 [RFC 0/4] sco: Another SCO socket option :) Frédéric Dalleau
2012-11-28 18:28 ` [RFC 1/4] Bluetooth: Add option for SCO socket codec Frédéric Dalleau
2012-11-28 18:28 ` [RFC 2/4] Bluetooth: Add option for SCO socket socket Frédéric Dalleau
2012-11-28 18:28 ` [RFC 3/4] Bluetooth: Use codec to create SCO connection Frédéric Dalleau
2012-11-28 18:28 ` [RFC 4/4] Bluetooth: Set link parameters for outgoing connections Frédéric Dalleau
2012-11-29  9:31   ` Andrei Emeltchenko [this message]
2012-11-29  8:41 ` [RFC 0/4] sco: Another SCO socket option :) Arnaud Mouiche

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=20121129093147.GA2574@aemeltch-MOBL1 \
    --to=andrei.emeltchenko.news@gmail.com \
    --cc=frederic.dalleau@linux.intel.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;
as well as URLs for NNTP newsgroup(s).