From: Hsin-chen Chuang <chharry@google.com>
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Cc: chromeos-bluetooth-upstreaming@chromium.org,
Hsin-chen Chuang <chharry@chromium.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 3/3] Bluetooth: Add ABI doc for sysfs isoc_alt
Date: Mon, 10 Feb 2025 18:32:26 +0800 [thread overview]
Message-ID: <20250210103244.646150-1-chharry@google.com> (raw)
In-Reply-To: <20250210183224.v3.1.If6f14aa2512336173a53fc3552756cd8a332b0a3@changeid>
From: Hsin-chen Chuang <chharry@chromium.org>
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@chromium.org>
---
(no changes since v1)
Documentation/ABI/stable/sysfs-class-bluetooth | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/Documentation/ABI/stable/sysfs-class-bluetooth b/Documentation/ABI/stable/sysfs-class-bluetooth
index 36be02471174..1168e0318e35 100644
--- a/Documentation/ABI/stable/sysfs-class-bluetooth
+++ b/Documentation/ABI/stable/sysfs-class-bluetooth
@@ -7,3 +7,15 @@ 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: 10-Feb-2025
+KernelVersion: 6.13
+Contact: linux-bluetooth@vger.kernel.org
+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 data is not a valid number, the write fails with -EINVAL.
+ The other failures are vendor specific.
--
2.48.1.502.g6dc24dfdaf-goog
next prev parent reply other threads:[~2025-02-10 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 10:32 [PATCH v3 1/3] Bluetooth: Fix possible race with userspace of sysfs isoc_alt Hsin-chen Chuang
2025-02-10 10:32 ` [PATCH v3 2/3] Bluetooth: Always allow SCO packets for user channel Hsin-chen Chuang
2025-02-10 10:32 ` Hsin-chen Chuang [this message]
2025-02-10 18:17 ` [PATCH v3 3/3] Bluetooth: Add ABI doc for sysfs isoc_alt Luiz Augusto von Dentz
2025-02-11 4:22 ` Hsin-chen Chuang
2025-02-11 22:00 ` Luiz Augusto von Dentz
2025-02-12 4:48 ` Hsin-chen Chuang
2025-02-10 11:30 ` [v3,1/3] Bluetooth: Fix possible race with userspace of " bluez.test.bot
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=20250210103244.646150-1-chharry@google.com \
--to=chharry@google.com \
--cc=chharry@chromium.org \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--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.