[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <c6a869fc-8b4a-4311-b14e-28a131d6a706@linux.dev>
Date: Wed, 29 Oct 2025 16:11:56 +0800
From: Cryolitia PukNgae <cryolitia.pukngae@...ux.dev>
To: Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
 Jun Zhan <zhanjun@...ontech.com>, 聂诚
 <niecheng1@...ontech.com>, Guan Wentao <guanwentao@...ontech.com>,
 Feng Yuan <fengyuan@...ontech.com>, kernel <kernel@...ontech.com>,
 Cryolitia PukNgae <cryolitia@...ontech.com>
Subject: [RFC] sound: add uevent notifications for jack events
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
Powered by blists - more mailing lists
 
