Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • M millipixels
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 29
    • Issues 29
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Librem5
  • millipixels
  • Issues
  • #18

Closed
Open
Created Aug 27, 2021 by Dorota Czaplejewicz@dorota.czaplejewiczMaintainer

React to camera getting enabled

The case that should be working:

https://source.puri.sm/Librem5/linux-next/-/issues/330#note_168594

  1. Camera switch off
  2. Megapixels starts (notifies that the camera is unavailable)
  3. Camera switch turned on

Result: Megapixels enters camera mode.

It's really 2 scenarios, because the camera may be in 2 different states, at least the way the big camera driver is implemented today. One: camera was never present, driver is unloaded. Two: camera was present, driver is loaded, but it was turned off later.

I'm not sure which method should be used to communicate the state change. It should ideally reflect the camera status and not the switch state. Perhaps rfkill: https://source.puri.sm/Librem5/linux-next/-/issues/298

Assignee
Assign to
Time tracking