Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
P
Plasma Phone Components
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 26
    • Issues 26
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Plasma
  • Plasma Phone Components
  • Issues
  • #50

Closed
Open
Opened Nov 16, 2020 by Bernhard Rosenkraenzer@beroDeveloper

Controlling the torch with DBus vs. sysfs

Hi, I've written a small tool that exposes LED controls over D-Bus (similar in intent, but not implementation, to iio-sensor-proxy) so people don't have to mess with the /sys interface directly. https://github.com/OpenMandrivaSoftware/ledcontrol

It's tested on PinePhone through qdbus --system at the moment, works for both the flash and the various small LEDs on the front side. It should work on any other device as well.

Would it make sense to use that rather than handling /sys files directly to control the torch in Plasma Mobile?

Will provide a patch if people agree it makes sense to do this.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: plasma/plasma-phone-components#50