From: "Frédéric DALLEAU" <frederic.dalleau@linux.intel.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v4 2/6] Bluetooth: Add SCO socket voice_setting option
Date: Tue, 09 Apr 2013 18:38:15 +0200 [thread overview]
Message-ID: <516443F7.7030207@linux.intel.com> (raw)
In-Reply-To: <EA2DBE3E-3266-4F27-BE89-87A6EB5979B8@holtmann.org>
Le 09/04/2013 17:30, Marcel Holtmann a écrit :
> Hi Fred,
>
>>>> #define SCO_SETTINGS 0x03
>>>> struct sco_settings {
>>>> __u16 settings;
>>>> };
>>>
>>> That is my current thinking. However we might start using SOL_BLUETOOTH and start using BT_VOICE or similar as a socket option. I do want to be able to retire SOL_SCO and SOL_L2CAP at some point.
>>
>> I just forgot about this because I don't use it and this API satisfy my needs, but it does not allow to distinguish between host side and adapter side mSBC.
>> Do you still care about this?
>
> what do you mean by host side and adapter side difference? I am not following.
I was thinking that an adapter could do some adapter side mSBC similar
to the way SCO over PCM works. (ie when connected the adapter
automatically encode and forward packet to/from his PCM port).
If it doesn't make sense, just forget about it.
The socket option would look like this (in bluetooth.h) :
#define BT_VOICE 11
struct bt_voice {
__u16 setting;
};
#define BT_VOICE_TRANSPARENT 0x0003
#define BT_VOICE_CVSD 0x0060
Regards,
Fred
next prev parent reply other threads:[~2013-04-09 16:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 18:04 [PATCH v4 0/6] sco: SCO socket option for voice_setting Frédéric Dalleau
2013-03-19 18:04 ` [PATCH v4 1/6] Bluetooth: Move and rename hci_conn_accept Frédéric Dalleau
2013-03-26 20:18 ` Marcel Holtmann
2013-03-19 18:04 ` [PATCH v4 2/6] Bluetooth: Add SCO socket voice_setting option Frédéric Dalleau
2013-03-26 20:22 ` Marcel Holtmann
2013-04-08 8:55 ` Dalleau, Frederic
2013-04-08 12:41 ` Frédéric DALLEAU
2013-04-08 17:50 ` Marcel Holtmann
2013-04-09 8:32 ` Frédéric DALLEAU
2013-04-09 15:30 ` Marcel Holtmann
2013-04-09 16:38 ` Frédéric DALLEAU [this message]
2013-03-19 18:04 ` [PATCH v4 3/6] Bluetooth: Use hci_connect_sco directly Frédéric Dalleau
2013-03-19 18:04 ` [PATCH v4 4/6] Bluetooth: Use voice_setting in incoming SCO connection Frédéric Dalleau
2013-03-19 18:04 ` [PATCH v4 5/6] Bluetooth: Parameters for outgoing SCO connections Frédéric Dalleau
2013-03-19 18:04 ` [PATCH v4 6/6] Bluetooth: Fallback transparent SCO from T2 to T1 Frédéric Dalleau
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=516443F7.7030207@linux.intel.com \
--to=frederic.dalleau@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.