Hi Sonny,
On Fri, Nov 20, 2020 at 1:00 PM Sonny Sasaka <sonnysasaka@xxxxxxxxxxxx> wrote:
>
> This patch add the documentation of the Battery Provider which lets
> external clients feed battery information to BlueZ if they are able to
> decode battery reporting via any profile. BlueZ UI clients can then use
> the org.bluez.Battery1 API as a single source of battery information
> coming from many different profiles.
>
> Reviewed-by: Miao-chen Chou <mcchou@xxxxxxxxxxxx>
>
> ---
> Changes in v3:
> * Remove doc duplication in BatteryProvider1 and mention that it's the
> same as Battery1 instead.
> * Suggest profile UUID in Source property.
>
> doc/battery-api.txt | 49 +++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 49 insertions(+)
>
> diff --git a/doc/battery-api.txt b/doc/battery-api.txt
> index dc7dbeda2..b5c9a7be1 100644
> --- a/doc/battery-api.txt
> +++ b/doc/battery-api.txt
> @@ -12,3 +12,52 @@ Object path [variable prefix]/{hci0,hci1,...}/dev_XX_XX_XX_XX_XX_XX
> Properties byte Percentage [readonly]
>
> The percentage of battery left as an unsigned 8-bit integer.
> +
> + string Source [readonly, optional, experimental]
> +
> + Describes where the battery information comes from
> + This property is informational only and may be useful
> + for debugging purposes.
> + Providers from BatteryProvider1 may make use of this
> + property to indicate where the battery report comes from
> + (e.g. "HFP 1.7", "HID", or the profile UUID).
We might need to remove the version number here since there is no
equivalent on UUID, in fact friendly names may be a bad idea after all
since for new profiles we may not have a friendly name to do the
translation and since this is property that would be hard to notify
the provider that we don't understand what is the Source while UUIDs,
if well formatted, should not have this problem so Id just get rid of
the use of friendly names altogether and expect the Source to be a
128bits UUID in string format.
> +
> +
> +Battery Provider Manager hierarchy
> +==================================
> +A battery provider starts by registering itself as a battery provider with the
> +RegisterBatteryProvider method passing an object path as the provider ID. Then,
> +it can start exposing org.bluez.BatteryProvider1 objects having the path
> +starting with the given provider ID. It can also remove objects at any time.
> +The objects and their properties exposed by battery providers will be reflected
> +on org.bluez.Battery1 interface.
> +
> +BlueZ will stop monitoring these exposed and removed objects after
> +UnregisterBatteryProvider is called for that provider ID.
> +
> +Service org.bluez
> +Interface org.bluez.BatteryProviderManager1 [experimental]
> +Object path /org/bluez/{hci0,hci1,...}
> +
> +Methods void RegisterBatteryProvider(object provider)
> +
> + This registers a battery provider. A registered
> + battery provider can then expose objects with
> + org.bluez.BatteryProvider1 interface described below.
We should probably mention this expects an object implementing
ObjectManaged in order to list the Battery1 provider.
> + void UnregisterBatteryProvider(object provider)
> +
> + This unregisters a battery provider. After
> + unregistration, the BatteryProvider1 objects provided
> + by this client are ignored by BlueZ.
> +
> +
> +Battery Provider hierarchy
> +==========================
> +
> +Service <client D-Bus address>
> +Interface org.bluez.BatteryProvider1 [experimental]
> +Object path {provider_root}/org/bluez/{hci0,hci1,...}/dev_XX_XX_XX_XX_XX_XX
If this is on the client the object path does not necessarily need to
follow our object hierarchy.
> +
> +Properties Objects provided on this interface contain the same properties
> + as org.bluez.Battery1 interface.
> --
> 2.26.2
--
Luiz Augusto von Dentz
