From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: shumingf@realtek.com
Cc: jikos@kernel.org, bentiss@kernel.org, broonie@kernel.org,
linux-input@vger.kernel.org, flove@realtek.com,
oder_chiou@realtek.com, jack.yu@realtek.com,
derek.fang@realtek.com, bard.liao@intel.com,
pierre-louis.bossart@linux.dev
Subject: Re: [PATCH 2/3] HID: core: Add bus define for SoundWire bus
Date: Wed, 11 Jun 2025 11:55:08 +0100 [thread overview]
Message-ID: <aElgjKSBXw6l6hFK@opensource.cirrus.com> (raw)
In-Reply-To: <20250611102650.563137-1-shumingf@realtek.com>
On Wed, Jun 11, 2025 at 06:26:50PM +0800, shumingf@realtek.com wrote:
Adding Pierre.
> From: Charles Keepax <ckeepax@opensource.cirrus.com>
>
> 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.
>
> Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
> ---
> drivers/hid/hid-core.c | 3 +++
> include/uapi/linux/input.h | 1 +
> 2 files changed, 4 insertions(+)
>
> diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
> index b348d0464314..b419e31005b8 100644
> --- a/drivers/hid/hid-core.c
> +++ b/drivers/hid/hid-core.c
> @@ -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;
> diff --git a/include/uapi/linux/input.h b/include/uapi/linux/input.h
> index 2557eb7b0561..127119c287cf 100644
> --- a/include/uapi/linux/input.h
> +++ b/include/uapi/linux/input.h
> @@ -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
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-06-11 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 10:26 [PATCH 2/3] HID: core: Add bus define for SoundWire bus shumingf
2025-06-11 10:53 ` Charles Keepax
2025-06-11 10:55 ` Charles Keepax [this message]
2025-06-13 11:41 ` Mark Brown
2025-06-16 2:17 ` Shuming [范書銘]
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=aElgjKSBXw6l6hFK@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=bard.liao@intel.com \
--cc=bentiss@kernel.org \
--cc=broonie@kernel.org \
--cc=derek.fang@realtek.com \
--cc=flove@realtek.com \
--cc=jack.yu@realtek.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=shumingf@realtek.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;
as well as URLs for NNTP newsgroup(s).