pm: use actions for device PM control

Instead of passing target states, use actions for device PM control.
Actions represent better the meaning of the callback argument.
Furthermore, they are more future proof as they can be suitable for
other PM actions that have no direct mapping to a state. If we compare
with Linux, we could have a multi-stage suspend/resume. Such scenario
would not have a good mapping when using target states.

Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
This commit is contained in:
Gerard Marull-Paretas 2021-07-05 15:13:40 +02:00 committed by Anas Nashif
commit 7ccc1a41bc
40 changed files with 176 additions and 145 deletions

View file

@ -439,11 +439,11 @@ static inline bool uart_npcx_device_is_transmitting(const struct device *dev)
}
static inline int uart_npcx_pm_control(const struct device *dev,
enum pm_device_state state)
enum pm_device_action action)
{
/* If next device power state is SUSPEND power state */
switch (state) {
case PM_DEVICE_STATE_SUSPENDED:
switch (action) {
case PM_DEVICE_ACTION_SUSPEND:
/*
* If uart device is busy with transmitting, the driver will
* stay in while loop and wait for the transaction is completed.