Hi, On 17-Dec-24 2:41 AM, Armin Wolf wrote: <snip> >> Regarding the keycode do you mean that this should send something to >> the input device via the sparse keymap or that the i8042 filter should >> emit a key event, or? And/or that it could be handled with a hwdb >> update in systemd so that this key gets mapped to the right event? > > Please send the input event through the input device with the sparse keymap. > >> >> Regarding the specific keycode I assume that maybe the appropriate one >> would be KEY_CAMERA_ACCESS_TOGGLE ? (though I have not seen any OSD >> notification with this keycode but maybe it was only with older >> versions of userspace tools I was originally testing this with..). > > Depends, that will happen if recording gets disabled? Since the driver handles the toggling of recording on/off itself KEY_CAMERA_ACCESS_TOGGLE should not be used. As mentioned in my reply to the v3 posting: "It would be good to report the camera state to userspace using a separate input/evdev device which reports SW_CAMERA_LENS_COVER as discussed here: https://lore.kernel.org/linux-media/CANiDSCtjpPG3XzaEOEeczZWO5gL-V_sj_Fv5=w82D6zKC9hnpw@xxxxxxxxxxxxxx/ the plan is to make that the canonical API to reported "muted" cameras." Regards, Hans
