7ccc1a41bc
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> |
||
---|---|---|
.. | ||
6lo | ||
all | ||
arp | ||
bridge | ||
buf | ||
checksum_offload | ||
context | ||
dhcpv4 | ||
ethernet_mgmt | ||
hostname | ||
icmpv4 | ||
icmpv6 | ||
ieee802154 | ||
iface | ||
igmp | ||
ip-addr | ||
ipv6 | ||
ipv6_fragment | ||
lib | ||
mgmt | ||
mld | ||
neighbor | ||
net_pkt | ||
pm | ||
ppp/driver | ||
promiscuous | ||
ptp/clock | ||
route | ||
route_mcast | ||
shell | ||
socket | ||
tcp2 | ||
traffic_class | ||
trickle | ||
tx_timestamp | ||
udp | ||
utils | ||
virtual | ||
vlan |