From: Cryolitia PukNgae <cryolitia.pukngae@linux.dev>
To: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
"Jun Zhan" <zhanjun@uniontech.com>, 聂诚 <niecheng1@uniontech.com>,
"Guan Wentao" <guanwentao@uniontech.com>,
"Feng Yuan" <fengyuan@uniontech.com>,
kernel <kernel@uniontech.com>,
"Cryolitia PukNgae" <cryolitia@uniontech.com>
Subject: [RFC] sound: add uevent notifications for jack events
Date: Wed, 29 Oct 2025 16:11:56 +0800 [thread overview]
Message-ID: <c6a869fc-8b4a-4311-b14e-28a131d6a706@linux.dev> (raw)
I propose adding uevent notifications for all audio jack events in the
sound subsystem, including headphone and microphone jacks.
The kernel already sends uevents for certain jack types like HDMI,
demonstrating this pattern is well-established. However, other common
audio jacks like headphones and microphones only generate input events,
not uevents.
This inconsistency affects userspace tools that rely on uevents for
device management. Adding uevents for all jack types would provide a
uniform interface for monitoring audio connection state changes.
My proposal is straightforward: extend the existing uevent mechanism to
cover all audio jack plug/unplug events in the sound subsystem. This
change would maintain backward compatibility with existing input event
consumers while providing consistent device notification for all jack
types.
The change aligns with the semantic purpose of uvents - to notify about
hardware state changes. Physical connection events naturally fit this
category.
If there are objections or historical context I should consider, I would
appreciate hearing them.
Thanks.
Best regards,
Cryolitia PukNgae
next reply other threads:[~2025-10-29 8:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 8:11 Cryolitia PukNgae [this message]
2025-10-31 11:36 ` [RFC] sound: add uevent notifications for jack events Takashi Iwai
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=c6a869fc-8b4a-4311-b14e-28a131d6a706@linux.dev \
--to=cryolitia.pukngae@linux.dev \
--cc=cryolitia@uniontech.com \
--cc=fengyuan@uniontech.com \
--cc=guanwentao@uniontech.com \
--cc=kernel@uniontech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=niecheng1@uniontech.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=zhanjun@uniontech.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