From: Hsin-chen Chuang <chharry@xxxxxxxxxxxx> The functionality was completed in commit 5e5c3898ef49 ("Bluetooth: Fix possible race with userspace of sysfs isoc_alt") Fixes: 5e5c3898ef49 ("Bluetooth: Fix possible race with userspace of sysfs isoc_alt") Signed-off-by: Hsin-chen Chuang <chharry@xxxxxxxxxxxx> --- (no changes since v1) Documentation/ABI/stable/sysfs-class-bluetooth | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/Documentation/ABI/stable/sysfs-class-bluetooth b/Documentation/ABI/stable/sysfs-class-bluetooth index 36be02471174..8cc5f3cfe133 100644 --- a/Documentation/ABI/stable/sysfs-class-bluetooth +++ b/Documentation/ABI/stable/sysfs-class-bluetooth @@ -7,3 +7,17 @@ Description: This write-only attribute allows users to trigger the vendor reset The reset may or may not be done through the device transport (e.g., UART/USB), and can also be done through an out-of-band approach such as GPIO. + +What: /sys/class/bluetooth/hci<index>/isoc_alt +Date: 22-Jan-2025 +KernelVersion: 6.13 +Contact: linux-bluetooth@xxxxxxxxxxxxxxx +Description: This attribute allows users to configure the USB Alternate setting + for the specific HCI device. Reading this attribute returns the + current setting, and writing any supported numbers would change + the setting. See the USB Alternate setting definition in Bluetooth + core spec 5, vol 4, part B, table 2.1. + If the HCI device doesn't support USB Alternate setting + configuration, the read/write fails with -ENODEV. + If the data is not a valid number, the write fails with -EINVAL. + The other failures are vendor specific. -- 2.48.1.262.g85cc9f2d1e-goog