xref: /aosp_15_r20/external/pigweed/pw_bluetooth/docs.rst (revision 61c4878ac05f98d0ceed94b57d316916de578985)

.. _module-pw_bluetooth:

============
pw_bluetooth
============
.. pigweed-module::
   :name: pw_bluetooth

The ``pw_bluetooth`` module contains APIs and utilities for the host layer of
Bluetooth Low Energy.

--------
Host API
--------
.. attention::

   This module is still under construction, the API is not yet stable.

The headers in ``public/pw_bluetooth`` constitute generic interfaces and types
for a Bluetooth Host API. Currently, only Low Energy APIs exist.

low_energy::Central2
====================
.. doxygenclass:: pw::bluetooth::low_energy::Central2
   :members:

low_energy::Peripheral2
=======================
.. doxygenclass:: pw::bluetooth::low_energy::Peripheral2
   :members:

low_energy::AdvertisedPeripheral2
=================================
.. doxygenclass:: pw::bluetooth::low_energy::AdvertisedPeripheral2
   :members:

low_energy::Connection2
=======================
.. doxygenclass:: pw::bluetooth::low_energy::Connection2
   :members:

low_energy::Channel
===================
.. doxygenclass:: pw::bluetooth::low_energy::Channel
   :members:


low_energy::ChannelListenerRegistry
===================================
.. doxygenclass:: pw::bluetooth::low_energy::ChannelListenerRegistry
   :members:

low_energy::ChannelListener
===================================
.. doxygenclass:: pw::bluetooth::low_energy::ChannelListener
   :members:

gatt::Server2
=============
.. doxygenclass:: pw::bluetooth::gatt::Server2
   :members:

gatt::LocalService2
===================
.. doxygenclass:: pw::bluetooth::gatt::LocalService2
   :members:

gatt::LocalServiceDelegate2
===========================
.. doxygenclass:: pw::bluetooth::gatt::LocalServiceDelegate2
   :members:

gatt::Client2
=============
.. doxygenclass:: pw::bluetooth::gatt::Client2
   :members:

gatt::RemoteService2
====================
.. doxygenclass:: pw::bluetooth::gatt::RemoteService2
   :members:

Controller2
===========
.. doxygenclass:: pw::bluetooth::Controller2
   :members:

----------------------------
Module Configuration Options
----------------------------
The following configurations can be adjusted via compile-time configuration of
this module, see the
:ref:`module documentation <module-structure-compile-time-configuration>` for
more details.

.. c:macro:: PW_BLUETOOTH_DESCRIPTOR_VEC_SIZE

  Controls the size of ``Vector<Descriptor>`` in the above APIs.

-------------------------
Emboss Packet Definitions
-------------------------
``pw_bluetooth`` contains `Emboss <https://github.com/google/emboss>`_ packet
definitions. So far, some packets and enums from the following protocols are
defined:

- HCI
- L2CAP
- H4

.. _module-pw_bluetooth-usage:

Usage
=====
1. Add Emboss to your project as described in
   :ref:`module-pw_third_party_emboss`.

.. tab-set::

   .. tab-item:: Bazel
      :sync: bazel

      2. Add the Emboss target you require to your build target's dependency
         list - for example, ``@pigweed//pw_bluetooth:emboss_hci_group`` for HCI
         packets.

   .. tab-item:: GN
      :sync: gn

      2. Add the Emboss target you require to your build target's dependency
         list - for example, ``$dir_pw_bluetooth/emboss_hci_group`` for HCI
         packets.

   .. tab-item:: CMake
      :sync: cmake

      2. Add the Emboss target you require to your build target's dependency
         list - for example, ``pw_bluetooth.emboss_hci_group`` for HCI packets.


3. Include the generated header files you require in your source files.

.. code-block:: cpp

   #include "pw_bluetooth/hci_commands.emb.h"
   #include "pw_bluetooth/hci_android.emb.h"

.. inclusive-language: disable

4. Construct an Emboss view over a buffer as described in the `Emboss User Guide
   <https://github.com/google/emboss/blob/master/doc/guide.md>`_.

.. inclusive-language: enable

.. literalinclude:: emboss_test.cc
   :language: cpp
   :start-after: [pw_bluetooth-examples-make_view]
   :end-before: [pw_bluetooth-examples-make_view]

.. note::

   When you first add generated headers, ``clangd`` may complain that the
   generated header files do not exist. You need to build your project to
   resolve this. Similarly, you need to rebuild in order for .emb file updates
   to be reflected in the generated headers.

.. _module-pw_bluetooth-contributing:

Contributing
============
Emboss ``.emb`` files can be edited to add additional packets and enums.

Emboss files should be formatted by running the following from the Pigweed root.

.. code-block:: bash

   (export EMBOSS_PATH="environment/packages/emboss" &&
       export PYTHONPATH+=":${EMBOSS_PATH}" &&
       python3 "${EMBOSS_PATH}/compiler/front_end/format.py" pw_bluetooth/public/pw_bluetooth/*.emb)

If adding files, be sure to update the GN, Bazel, and CMake build rules.
Presubmit runs the ``emboss_test.cc`` test on all three.


Size Report
===========
Delta of +972 when constructing the first packet view and reading/writing a
field. This includes the runtime library and the 4-byte buffer.

.. include:: emboss_size_report

Delta of +96 when adding a second packet view and reading/writing a field.

.. include:: emboss_size_report_diff

-------
Roadmap
-------
- Bluetooth Proxy (WIP in in :ref:`module-pw_bluetooth_proxy`)
- Add automated Emboss file formatting to `pw format` (:bug:`331195584`)
- Create a backend for the Bluetooth API using Fuchsia's Bluetooth stack
  (Sapphire).
- Stabilize the Bluetooth API.
- Add BR/EDR APIs.