HID: core: Add bus define for SoundWire bus
Subsystems (3)
PATCH v2 2/3 HID: core: Add bus define for SoundWire bus
From: Charles Keepax <[email protected]>
SDCA (SoundWire Device Class for Audio) uses HID to convey input events from peripheral devices. Add a bus define for the SoundWire bus to prepare support for this.
--- drivers/hid/hid-core.c | 3 +++ include/uapi/linux/input.h | 1 + 2 files changed, 4 insertions(+)
drivers/hid/hid-core.c +3 -0
@@ -2294,6 +2294,9 @@ int hid_connect(struct hid_device *hdev, unsigned int connect_mask)case BUS_I2C : bus ="I2C" ;break ; +case BUS_SDW : + bus ="SOUNDWIRE" ; +break ;case BUS_VIRTUAL : bus ="VIRTUAL" ;break ;
include/uapi/linux/input.h +1 -0
@@ -275,6 +275,7 @@ struct input_mask {#define BUS_CEC 0x1E#define BUS_INTEL_ISHTP 0x1F#define BUS_AMD_SFH 0x20 +#define BUS_SDW 0x21/* * MT_TOOL types
Signature · 1 line
2.34.1
Quoted 5 lines · On Mon, Jun 16, 2025 at 07:49:07PM +0800, [email protected] wrote:
From: Charles Keepax <[email protected]>
SDCA (SoundWire Device Class for Audio) uses HID to convey input events from peripheral devices. Add a bus define for the SoundWire bus to prepare support for this.
This seems mostly an ASoC series, is it OK to take this via ASoC?
Quoted 7 lines · Mark Brown
Quoted 5 lines
From: Charles Keepax <[email protected]>
SDCA (SoundWire Device Class for Audio) uses HID to convey input events from peripheral devices. Add a bus define for the SoundWire bus to prepare support for this.
This seems mostly an ASoC series, is it OK to take this via ASoC?
That's fine with me, feel free to add
for the HID bits. Thanks,
Signature · 2 lines
Jiri Kosina SUSE Labs
Quoted 5 lines · On Mon, 16 Jun 2025 19:49:07 +0800, [email protected] wrote:
SDCA (SoundWire Device Class for Audio) uses HID to convey input events from peripheral devices. Add a bus define for the SoundWire bus to prepare support for this.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[2/3] HID: core: Add bus define for SoundWire bus
commit: 3421d46440ebe0865bec71dbd2330b4e17a425ab
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark