linux-kernel - Re: [PATCH 0/3] Bluetooth: btusb: MediaTek ISO data transmission support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CABBYNZLEWCFo_OWvPxaM54S65-mAhZ-3R1XgRqb-UnUChcJV9w@mail.gmail.com>
Date: Wed, 29 May 2024 11:21:05 -0400
From: Luiz Augusto von Dentz <luiz.dentz@...il.com>
To: Chris Lu <chris.lu@...iatek.com>
Cc: Marcel Holtmann <marcel@...tmann.org>, Johan Hedberg <johan.hedberg@...il.com>, 
	Sean Wang <sean.wang@...iatek.com>, Deren Wu <deren.Wu@...iatek.com>, 
	Aaron Hou <aaron.hou@...iatek.com>, Steve Lee <steve.lee@...iatek.com>, 
	linux-bluetooth <linux-bluetooth@...r.kernel.org>, 
	linux-kernel <linux-kernel@...r.kernel.org>, 
	linux-mediatek <linux-mediatek@...ts.infradead.org>
Subject: Re: [PATCH 0/3] Bluetooth: btusb: MediaTek ISO data transmission support

Hi,

On Tue, May 28, 2024 at 11:30 PM Chris Lu <chris.lu@...iatek.com> wrote:
>
> Since SIG hasn't clearly defined the specification about ISO data over USB
> transmission yet, MediaTek adopts a method by adding an additional interrupt
> endpoint for ISO data transmission which is different from current way
> on Bluetooth upstream driver using existed bulk. Interrupt endpoint has
> guaranteed bandwidth, sufficient max data length for LE audio packet and
> support error checking. These characteristics are similar to the use of ISO data.
>
> Chris Lu (3):
>   Bluetooth: net: add hci_iso_hdr function for iso data
>   Bluetooth: btmtk: add macro to get/set/clear MediaTek defined flags
>   Bluetooth: btusb: mediatek: add MediaTek ISO data transmission
>     function
>
>  drivers/bluetooth/btmtk.c   |  35 +++++
>  drivers/bluetooth/btmtk.h   |  46 ++++++
>  drivers/bluetooth/btusb.c   | 293 +++++++++++++++++++++++++++++++++++-
>  include/net/bluetooth/hci.h |   5 +
>  4 files changed, 378 insertions(+), 1 deletion(-)

This probably needs to be handled in btmtk.c though, since it is not
standard we shall avoid having vendor specific transports like this in
btusb.c


-- 
Luiz Augusto von Dentz