From: Chris Lu <chris.lu@mediatek.com>
To: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Von Dentz <luiz.dentz@gmail.com>
Cc: Sean Wang <sean.wang@mediatek.com>,
Deren Wu <deren.Wu@mediatek.com>,
Aaron Hou <aaron.hou@mediatek.com>,
Steve Lee <steve.lee@mediatek.com>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mediatek <linux-mediatek@lists.infradead.org>,
Chris Lu <chris.lu@mediatek.com>
Subject: [PATCH v3 0/4] Bluetooth: btusb: MediaTek ISO data transmission
Date: Thu, 6 Jun 2024 17:23:36 +0800 [thread overview]
Message-ID: <20240606092340.27675-1-chris.lu@mediatek.com> (raw)
Since SIG has not yet clearly defined the specification for ISO data
transmission over USB, MediaTek has adopted a method of adding an
additional interrupt endpoint for ISO data transmission. This approach
differs from the current method used in the Bluetooth upstream driver,
which utilizes existing bulk endpoints. The interrupt endpoint provides
guaranteed bandwidth, sufficient maximum data length for ISO packets
and error checking.
Certain new functions related to USB transportation, such as urb
allocation and submission, are implemented in btusb.c to leverage
existing functions and data structures defined therein. Meanwhile,
vendor-specific functions unrelated to transportation have been moved
to btmtk.c to streamline btusb.c.
Chris Lu (4):
Bluetooth: net: add hci_iso_hdr function for iso data
Bluetooth: btusb: add callback function in btusb suspend/resume
Bluetooth: btmtk: add macro to get/set/clear MediaTek defined flags
Bluetooth: btusb: mediatek: add ISO data transmission functions
drivers/bluetooth/btmtk.c | 92 ++++++++++++
drivers/bluetooth/btmtk.h | 61 ++++++++
drivers/bluetooth/btusb.c | 276 ++++++++++++++++++++++++++++++++++++
include/net/bluetooth/hci.h | 5 +
4 files changed, 434 insertions(+)
--
2.18.0
next reply other threads:[~2024-06-06 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 9:23 Chris Lu [this message]
2024-06-06 9:23 ` [PATCH v3 1/4] Bluetooth: net: add hci_iso_hdr function for iso data Chris Lu
2024-06-06 9:56 ` Bluetooth: btusb: MediaTek ISO data transmission bluez.test.bot
2024-06-06 9:23 ` [PATCH v3 2/4] Bluetooth: btusb: add callback function in btusb suspend/resume Chris Lu
2024-06-06 9:23 ` [PATCH v3 3/4] Bluetooth: btmtk: add macro to get/set/clear MediaTek defined flags Chris Lu
2024-06-06 9:23 ` [PATCH v3 4/4] Bluetooth: btusb: mediatek: add ISO data transmission functions Chris Lu
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=20240606092340.27675-1-chris.lu@mediatek.com \
--to=chris.lu@mediatek.com \
--cc=aaron.hou@mediatek.com \
--cc=deren.Wu@mediatek.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=sean.wang@mediatek.com \
--cc=steve.lee@mediatek.com \
/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