Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • L libfprint
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 66
    • Issues 66
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • libfprint
  • libfprint
  • Issues
  • #409

Closed
Open
Created Aug 09, 2021 by Benjamin Berg@benzeaOwner

goodixmoc: Implement suspend/resume

With !270 (closed), it is now possible to support verifying/identifying for a long period of time, including while the laptop is suspended. libfprint will correctly configure USB wakeup when needed.

In general, all that is needed should be implementing suspend and resume methods that stop/start the urbs to query the device state. You can use the new fpi_device_critical_enter and fpi_device_critical_leave to ensure the driver is in the correct state to suspend/resume.

An working example is the synaptics driver, see:

  • d547c000 which makes use of the critical section API
  • 5c89bda7 which implements suspend/resume

If you have any questions, please ping me. This is relatively low-priority for now, as it requires more changes in gnome-shell, GDM and fprintd to work correctly.

CC: @bogerwang

Assignee
Assign to
Time tracking