Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mouse availability signaling and YubiKey configuration #4

Merged
merged 4 commits into from Oct 25, 2021

Conversation

spiiroin
Copy link
Contributor

No description provided.

Fix integer and integer vs pointer size issues.

Signed-off-by: Simo Piiroinen <simo.piiroinen@jolla.com>
Device names are more or less free form text, which makes them
less than ideal for use as configuration entry keys.

There are devices that can have multiple functions i.e. there
can be several input device nodes that can't be told apart
based on vendor-product information.

Make it possible to define device to be configured also by
using udev/modalias style bus, vendor and product id key.

Make it possible to override heuristics conditionally based on
probed device type i.e. configuration can be done in terms of
device identification and the type mce would have arrived to by
default.

Add a placeholder configuration file that acts also as
documentation for the feature.

Signed-off-by: Simo Piiroinen <simo.piiroinen@jolla.com>
@spiiroin spiiroin changed the title Mouse availability signaling Mouse availability signaling and YubiKey configuration Oct 15, 2021
@jpetrell
Copy link

I can get mouse state listening to work, but MCE_HARDWARE_MOUSE_STATE_GET method call returns an error for some reason.

@spiiroin
Copy link
Contributor Author

I can get mouse state listening to work, but MCE_HARDWARE_MOUSE_STATE_GET method call returns an error for some reason.

New method calls need to be made allowed-for-user and I forgot to do that. Will fix.

rpm/mce.spec Outdated Show resolved Hide resolved
MCE needs to track appearing and disappearing input devices
and gauge type of each input device currently available.

Some of this state information is also exposed over D-Bus,
e.g. availability of hardware keyboard is used by UI side
to decide whether virtual keyboard should be shown or not.

Differentiate between touch and mouse input devices within
MCE, keep track of mouse device availability, and expose
availability state on D-Bus as an enabler for UI showing or
hiding mouse cursor.

Signed-off-by: Simo Piiroinen <simo.piiroinen@jolla.com>
…5731

Based on input device capabilities YubiKey USB dongles look like full
blown keyboards. This leads to virtual keyboard getting disabled when
such dongle is attached.

Add mce input device type configuration file that labels YubiKey devices
as "user activity tracking only" type - using the dongle postpones
display blanking etc, but does not affect virtual keyboard visibility.

Signed-off-by: Simo Piiroinen <simo.piiroinen@jolla.com>
@spiiroin
Copy link
Contributor Author

Review commits squashed

@spiiroin spiiroin merged commit d7a5172 into sailfishos:master Oct 25, 2021
@spiiroin spiiroin deleted the jb55731_mouse_availability branch October 25, 2021 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants