From: Joseph Hwang <josephsih@chromium.org>
To: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com
Cc: josephsih@google.com,
chromeos-bluetooth-upstreaming@chromium.org,
Joseph Hwang <josephsih@chromium.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH v1 0/2] To support the HFP WBS, a chip vendor may choose a particular
Date: Thu, 13 Aug 2020 16:41:27 +0800 [thread overview]
Message-ID: <20200813084129.332730-1-josephsih@chromium.org> (raw)
USB alternate seeting of which the packet size is distinct.
The patches are to expose the packet size to user space so that
the user space does not need to hard code those values.
We have verified this patch on Chromebooks which use
- Realtek 8822CE controller with USB alt setting 1
- Intel controller with USB alt setting 6
Our user space audio server, cras, can get the correct
packet length from the socket option.
Joseph Hwang (2):
Bluetooth: btusb: define HCI packet sizes of USB Alts
Bluetooth: sco: expose WBS packet length in socket option
drivers/bluetooth/btusb.c | 43 +++++++++++++++++++++++--------
include/net/bluetooth/bluetooth.h | 2 ++
include/net/bluetooth/hci_core.h | 1 +
net/bluetooth/sco.c | 8 ++++++
4 files changed, 43 insertions(+), 11 deletions(-)
--
2.28.0.236.gb10cc79966-goog
next reply other threads:[~2020-08-13 8:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 8:41 Joseph Hwang [this message]
2020-08-13 8:41 ` [PATCH v1 1/2] Bluetooth: btusb: define HCI packet sizes of USB Alts Joseph Hwang
2020-08-14 20:07 ` Luiz Augusto von Dentz
2020-08-19 14:38 ` Pali Rohár
2020-08-13 8:41 ` [PATCH v1 2/2] Bluetooth: sco: expose WBS packet length in socket option Joseph Hwang
2020-08-14 19:56 ` Luiz Augusto von Dentz
2020-08-19 14:37 ` Pali Rohár
2020-08-19 18:21 ` Luiz Augusto von Dentz
2020-08-19 18:23 ` Pali Rohár
2020-08-19 18:25 ` Luiz Augusto von Dentz
2020-08-19 2:48 ` [PATCH v1 0/2] To support the HFP WBS, a chip vendor may choose a particular Shyh-In Hwang
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=20200813084129.332730-1-josephsih@chromium.org \
--to=josephsih@chromium.org \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=josephsih@google.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@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).