Commit 817813c5 authored by David Boddie's avatar David Boddie
Browse files

Add information about LED APIs

parent 7b8377b6
Pipeline #54317 passed with stage
in 1 minute and 15 seconds
...@@ -4,11 +4,13 @@ ...@@ -4,11 +4,13 @@
Application-Level APIs Application-Level APIs
====================== ======================
Applications access software and hardware features of the phone using a number of APIs. Some features are not directly accessible to applications. Applications access software and hardware features of the phone using a number of APIs. Some features are not directly accessible to applications, either because they lack a suitable API that can be accessed from a Flatpak sandbox, or because they require elevated privileges on the underlying system.
.. contents:: .. contents::
:local: :local:
Lower level access to features is described in some detail in the :ref:`devkit_howto` for the Librem 5 development kit.
Audio Audio
----- -----
...@@ -42,6 +44,11 @@ Inertial Module ...@@ -42,6 +44,11 @@ Inertial Module
This sensor can be read and monitored using the ``net.hadess.SensorProxy`` D-Bus interface provided by the `iio-sensor-proxy`_ daemon. This is described in the `net.hadess.SensorProxy`_ documentation. This sensor can be read and monitored using the ``net.hadess.SensorProxy`` D-Bus interface provided by the `iio-sensor-proxy`_ daemon. This is described in the `net.hadess.SensorProxy`_ documentation.
LEDs
----
The LEDs are accessed using the using the ``org.sigxcpu.Feedback`` D-Bus interface provided by the `feedbackd`_ daemon. This is described in the `feedbackd D-Bus interface`_ documentation.
Modem/WWAN Modem/WWAN
---------- ----------
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment