Lines Matching refs:power

27 The PM code makes calls into the BTM module to set various power
35 Overall power states are managed *per device*, not per connection, but the power
36 policy is determined by the greatest allowable power action defined across all
40 states it wants ACTIVE, the power management code will change to ACTIVE.
44 The tables that determine which power levels are acceptable for which profiles
52 power modes are acceptable and what actions to take for each event.
63     from `bta_dm_conn_srvcs` and no longer be considered for power management
71   - `BTA_DM_PM_ACTIVE` is full-on power.
73     timeout is possible to be set, which effectively allows a power operation to
79 `bta_dm_pm_cback` with the bta sys module for incoming power management events,
83 At this point, the power managment code is basically done until the first set of
86 Throughout the `bta_dm_pm.cc` file, connections whose power management states are
98      - The power mode config is looked up in the `bta_dm_pm_cfg` table. If none
103      - The power spec state table (`bta_dm_pm_spec`) is checked to see if
107        connection if it's supposed to be managed according to the power spec
123        the first power management action didn't timeout (or was never attempted,
128        `BTA_DM_PM_NO_ACTION`. Only the highest power mode action is chosen from
132      - If a timeout is specified in the power spec table, then an unused timer
166      - If the status is `BTM_PM_STS_ACTIVE` (still in the ACTIVE power mode),
180        previous low power mode in the peer device's `prev_low` field.