Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
L
libfprint
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 14
    • Merge Requests 14
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • libfprint
  • libfprint
  • Issues
  • #256

Closed
Open
Opened May 05, 2020 by Prasad Hegde@prasad.hegdeDeveloper

Support for capture during suspend (including automatic wakeup)

The following is the windows lock and unlock behavior with sleep enabled for the devices. The same behavior is expected in linux too to save power.

Windows (Host PC) <-> Device <-> FP Sensor

  1. When windows lock happens, windows sends a command to start capture and waits for the interrupt indefinitely.
  2. Device gets the start capture command and notifies the sensor that be ready for the capture, enables the capture complete callback, and device sleeps.
  3. Now Windows is locked, waiting for the capture interrupt from the device and device is sleeping and maybe sensor also sleeping waiting for the finger event (depends on firmware)
  4. Now user places finger on the sensor for unlocking (without hitting any button or something).
  5. This event triggers the sensor, it captures the finger, wakes up the device and calls the capture complete callback of the device.
  6. Device notifies (or interrupts) the Windows host which is waiting for the capture interrupt indefinitely.
  7. Windows then sends the Identify command and gets the result.
  8. Finger matching happens in device, it sends the finger OK/NOT OK result, then the Windows unlocks depending on the result.

So here if you see, the device need not be active always, it can go to sleep to save the power, but still does the job!!

Edited May 05, 2020 by Benjamin Berg
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: libfprint/libfprint#256