2019-04-04 00:04:43 +02:00
|
|
|
|
2019-04-04 00:06:15 +02:00
|
|
|
|
2019-04-04 00:04:43 +02:00
|
|
|
|
2018-11-21 01:35:19 +01:00
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2019-04-04 00:06:15 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
|
|
|
|
|
2020-09-29 09:20:06 +02:00
|
|
|
|
2017-02-20 15:26:21 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
2020-09-29 09:20:06 +02:00
|
|
|
|
2017-02-20 15:26:21 +01:00
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2020-09-29 09:20:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-20 15:26:21 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-23 21:20:15 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-29 09:20:06 +02:00
|
|
|
|
2017-02-20 15:26:21 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-23 21:20:15 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2011-11-23 21:20:15 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2021-06-16 08:27:16 +02:00
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2025-09-18 06:04:30 +08:00
|
|
|
|
PM: Handle device registrations during suspend/resume
Modify the PM core to protect its data structures, specifically the
dpm_active list, from being corrupted if a child of the currently
suspending device is registered concurrently with its ->suspend()
callback. In that case, since the new device (the child) is added
to dpm_active after its parent, the PM core will attempt to
suspend it after the parent, which is wrong.
Introduce a new member of struct dev_pm_info, called 'sleeping',
and use it to check if the parent of the device being added to
dpm_active has been suspended, in which case the device registration
fails. Also, use 'sleeping' for checking if the ordering of devices
on dpm_active is correct.
Introduce variable 'all_sleeping' that will be set to 'true' once all
devices have been suspended and make new device registrations fail
until 'all_sleeping' is reset to 'false', in order to avoid having
unsuspended devices around while the system is going into a sleep state.
Remove pm_sleep_rwsem which is not necessary any more.
Special thanks to Alan Stern for discussions and suggestions that
lead to the creation of this patch.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-03-12 00:57:22 +01:00
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
PM: Handle device registrations during suspend/resume
Modify the PM core to protect its data structures, specifically the
dpm_active list, from being corrupted if a child of the currently
suspending device is registered concurrently with its ->suspend()
callback. In that case, since the new device (the child) is added
to dpm_active after its parent, the PM core will attempt to
suspend it after the parent, which is wrong.
Introduce a new member of struct dev_pm_info, called 'sleeping',
and use it to check if the parent of the device being added to
dpm_active has been suspended, in which case the device registration
fails. Also, use 'sleeping' for checking if the ordering of devices
on dpm_active is correct.
Introduce variable 'all_sleeping' that will be set to 'true' once all
devices have been suspended and make new device registrations fail
until 'all_sleeping' is reset to 'false', in order to avoid having
unsuspended devices around while the system is going into a sleep state.
Remove pm_sleep_rwsem which is not necessary any more.
Special thanks to Alan Stern for discussions and suggestions that
lead to the creation of this patch.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Pavel Machek <pavel@ucw.cz>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-03-12 00:57:22 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-19 01:18:57 +02:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2011-12-18 00:34:13 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-23 21:18:39 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2011-11-23 21:18:39 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2011-11-23 21:18:39 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-11-23 21:18:39 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2011-11-23 21:18:39 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2011-12-18 00:34:13 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2011-12-18 00:34:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2013-05-13 02:42:11 +00:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2011-05-17 23:26:00 +02:00
|
|
|
|
2011-11-23 21:19:57 +01:00
|
|
|
|
PM: Document rules on using pm_runtime_resume() in system suspend callbacks
It quite often is necessary to resume devices from runtime suspend
during system suspend for various reasons (for example, if their
wakeup settings need to be changed), but that requires middle-layer
or subsystem code to follow additional rules which currently are not
clearly documented.
Namely, if a driver calls pm_runtime_resume() for the device from
its ->suspend (or equivalent) system sleep callback, that may not
work if the middle layer above it has updated the state of the
device from its ->prepare or ->suspend callbacks already in an
incompatible way. For this reason, all middle layers must follow
the rule that, until the ->suspend callback provided by the device's
driver is invoked, the only way in which the device's state can be
updated is by calling pm_runtime_resume() for it, if necessary.
Fortunately enough, all middle layers in the code base today follow
this rule, but it is not explicitly stated anywhere, so do that.
Note that calling pm_runtime_resume() from the ->suspend callback
of a driver will cause the ->runtime_resume callback provided by the
middle layer to be invoked, but the rule above guarantees that this
callback will nest properly with the middle layer's ->suspend
callback and it will play well with the ->prepare one invoked before.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-09-20 02:26:00 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2014-05-16 02:47:37 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2014-05-16 02:47:37 +02:00
|
|
|
|
2015-07-15 14:40:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2015-07-15 14:40:06 +02:00
|
|
|
|
|
|
|
|
|
PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags
The motivation for this change is to provide a way to work around
a problem with the direct-complete mechanism used for avoiding
system suspend/resume handling for devices in runtime suspend.
The problem is that some middle layer code (the PCI bus type and
the ACPI PM domain in particular) returns positive values from its
system suspend ->prepare callbacks regardless of whether the driver's
->prepare returns a positive value or 0, which effectively prevents
drivers from being able to control the direct-complete feature.
Some drivers need that control, however, and the PCI bus type has
grown its own flag to deal with this issue, but since it is not
limited to PCI, it is better to address it by adding driver flags at
the core level.
To that end, add a driver_flags field to struct dev_pm_info for flags
that can be set by device drivers at the probe time to inform the PM
core and/or bus types, PM domains and so on on the capabilities and/or
preferences of device drivers. Also add two static inline helpers
for setting that field and testing it against a given set of flags
and make the driver core clear it automatically on driver remove
and probe failures.
Define and document two PM driver flags related to the direct-
complete feature: NEVER_SKIP and SMART_PREPARE that can be used,
respectively, to indicate to the PM core that the direct-complete
mechanism should never be used for the device and to inform the
middle layer code (bus types, PM domains etc) that it can only
request the PM core to use the direct-complete mechanism for
the device (by returning a positive value from its ->prepare
callback) if it also has been requested by the driver.
While at it, make the core check pm_runtime_suspended() when
setting power.direct_complete so that it doesn't need to be
checked by ->prepare callbacks.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-10-25 14:12:29 +02:00
|
|
|
|
2020-04-18 18:53:01 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags
The motivation for this change is to provide a way to work around
a problem with the direct-complete mechanism used for avoiding
system suspend/resume handling for devices in runtime suspend.
The problem is that some middle layer code (the PCI bus type and
the ACPI PM domain in particular) returns positive values from its
system suspend ->prepare callbacks regardless of whether the driver's
->prepare returns a positive value or 0, which effectively prevents
drivers from being able to control the direct-complete feature.
Some drivers need that control, however, and the PCI bus type has
grown its own flag to deal with this issue, but since it is not
limited to PCI, it is better to address it by adding driver flags at
the core level.
To that end, add a driver_flags field to struct dev_pm_info for flags
that can be set by device drivers at the probe time to inform the PM
core and/or bus types, PM domains and so on on the capabilities and/or
preferences of device drivers. Also add two static inline helpers
for setting that field and testing it against a given set of flags
and make the driver core clear it automatically on driver remove
and probe failures.
Define and document two PM driver flags related to the direct-
complete feature: NEVER_SKIP and SMART_PREPARE that can be used,
respectively, to indicate to the PM core that the direct-complete
mechanism should never be used for the device and to inform the
middle layer code (bus types, PM domains etc) that it can only
request the PM core to use the direct-complete mechanism for
the device (by returning a positive value from its ->prepare
callback) if it also has been requested by the driver.
While at it, make the core check pm_runtime_suspended() when
setting power.direct_complete so that it doesn't need to be
checked by ->prepare callbacks.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-10-25 14:12:29 +02:00
|
|
|
|
|
|
|
|
|
2025-02-11 16:00:02 +05:30
|
|
|
|
PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags
The motivation for this change is to provide a way to work around
a problem with the direct-complete mechanism used for avoiding
system suspend/resume handling for devices in runtime suspend.
The problem is that some middle layer code (the PCI bus type and
the ACPI PM domain in particular) returns positive values from its
system suspend ->prepare callbacks regardless of whether the driver's
->prepare returns a positive value or 0, which effectively prevents
drivers from being able to control the direct-complete feature.
Some drivers need that control, however, and the PCI bus type has
grown its own flag to deal with this issue, but since it is not
limited to PCI, it is better to address it by adding driver flags at
the core level.
To that end, add a driver_flags field to struct dev_pm_info for flags
that can be set by device drivers at the probe time to inform the PM
core and/or bus types, PM domains and so on on the capabilities and/or
preferences of device drivers. Also add two static inline helpers
for setting that field and testing it against a given set of flags
and make the driver core clear it automatically on driver remove
and probe failures.
Define and document two PM driver flags related to the direct-
complete feature: NEVER_SKIP and SMART_PREPARE that can be used,
respectively, to indicate to the PM core that the direct-complete
mechanism should never be used for the device and to inform the
middle layer code (bus types, PM domains etc) that it can only
request the PM core to use the direct-complete mechanism for
the device (by returning a positive value from its ->prepare
callback) if it also has been requested by the driver.
While at it, make the core check pm_runtime_suspended() when
setting power.direct_complete so that it doesn't need to be
checked by ->prepare callbacks.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-10-25 14:12:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
PM: Document rules on using pm_runtime_resume() in system suspend callbacks
It quite often is necessary to resume devices from runtime suspend
during system suspend for various reasons (for example, if their
wakeup settings need to be changed), but that requires middle-layer
or subsystem code to follow additional rules which currently are not
clearly documented.
Namely, if a driver calls pm_runtime_resume() for the device from
its ->suspend (or equivalent) system sleep callback, that may not
work if the middle layer above it has updated the state of the
device from its ->prepare or ->suspend callbacks already in an
incompatible way. For this reason, all middle layers must follow
the rule that, until the ->suspend callback provided by the device's
driver is invoked, the only way in which the device's state can be
updated is by calling pm_runtime_resume() for it, if necessary.
Fortunately enough, all middle layers in the code base today follow
this rule, but it is not explicitly stated anywhere, so do that.
Note that calling pm_runtime_resume() from the ->suspend callback
of a driver will cause the ->runtime_resume callback provided by the
middle layer to be invoked, but the rule above guarantees that this
callback will nest properly with the middle layer's ->suspend
callback and it will play well with the ->prepare one invoked before.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-09-20 02:26:00 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
|
|
|
|
|
PM: Document rules on using pm_runtime_resume() in system suspend callbacks
It quite often is necessary to resume devices from runtime suspend
during system suspend for various reasons (for example, if their
wakeup settings need to be changed), but that requires middle-layer
or subsystem code to follow additional rules which currently are not
clearly documented.
Namely, if a driver calls pm_runtime_resume() for the device from
its ->suspend (or equivalent) system sleep callback, that may not
work if the middle layer above it has updated the state of the
device from its ->prepare or ->suspend callbacks already in an
incompatible way. For this reason, all middle layers must follow
the rule that, until the ->suspend callback provided by the device's
driver is invoked, the only way in which the device's state can be
updated is by calling pm_runtime_resume() for it, if necessary.
Fortunately enough, all middle layers in the code base today follow
this rule, but it is not explicitly stated anywhere, so do that.
Note that calling pm_runtime_resume() from the ->suspend callback
of a driver will cause the ->runtime_resume callback provided by the
middle layer to be invoked, but the rule above guarantees that this
callback will nest properly with the middle layer's ->suspend
callback and it will play well with the ->prepare one invoked before.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-09-20 02:26:00 +02:00
|
|
|
|
|
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PM: Document rules on using pm_runtime_resume() in system suspend callbacks
It quite often is necessary to resume devices from runtime suspend
during system suspend for various reasons (for example, if their
wakeup settings need to be changed), but that requires middle-layer
or subsystem code to follow additional rules which currently are not
clearly documented.
Namely, if a driver calls pm_runtime_resume() for the device from
its ->suspend (or equivalent) system sleep callback, that may not
work if the middle layer above it has updated the state of the
device from its ->prepare or ->suspend callbacks already in an
incompatible way. For this reason, all middle layers must follow
the rule that, until the ->suspend callback provided by the device's
driver is invoked, the only way in which the device's state can be
updated is by calling pm_runtime_resume() for it, if necessary.
Fortunately enough, all middle layers in the code base today follow
this rule, but it is not explicitly stated anywhere, so do that.
Note that calling pm_runtime_resume() from the ->suspend callback
of a driver will cause the ->runtime_resume callback provided by the
middle layer to be invoked, but the rule above guarantees that this
callback will nest properly with the middle layer's ->suspend
callback and it will play well with the ->prepare one invoked before.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-09-20 02:26:00 +02:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2012-01-29 20:38:29 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2012-01-29 20:38:29 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2020-09-29 12:38:37 +02:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2013-05-13 02:42:11 +00:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-01-29 20:38:29 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-16 02:47:37 +02:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
2014-05-16 02:47:37 +02:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-18 06:04:30 +08:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-01-29 20:38:29 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-01-29 20:38:29 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2013-05-13 02:42:11 +00:00
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2012-01-29 20:38:29 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2011-02-16 21:53:17 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-02-16 21:53:17 +01:00
|
|
|
|
2021-06-16 08:27:16 +02:00
|
|
|
|
2011-02-16 21:53:17 +01:00
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2012-07-03 09:27:24 +00:00
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-09-29 09:20:06 +02:00
|
|
|
|
|
|
|
|
|
2017-02-20 15:26:21 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2021-06-16 08:27:16 +02:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:42 +01:00
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
2006-08-10 16:38:28 -07:00
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2010-03-26 23:53:55 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-16 15:20:36 -07:00
|
|
|
|
PM: Document rules on using pm_runtime_resume() in system suspend callbacks
It quite often is necessary to resume devices from runtime suspend
during system suspend for various reasons (for example, if their
wakeup settings need to be changed), but that requires middle-layer
or subsystem code to follow additional rules which currently are not
clearly documented.
Namely, if a driver calls pm_runtime_resume() for the device from
its ->suspend (or equivalent) system sleep callback, that may not
work if the middle layer above it has updated the state of the
device from its ->prepare or ->suspend callbacks already in an
incompatible way. For this reason, all middle layers must follow
the rule that, until the ->suspend callback provided by the device's
driver is invoked, the only way in which the device's state can be
updated is by calling pm_runtime_resume() for it, if necessary.
Fortunately enough, all middle layers in the code base today follow
this rule, but it is not explicitly stated anywhere, so do that.
Note that calling pm_runtime_resume() from the ->suspend callback
of a driver will cause the ->runtime_resume callback provided by the
middle layer to be invoked, but the rule above guarantees that this
callback will nest properly with the middle layer's ->suspend
callback and it will play well with the ->prepare one invoked before.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-09-20 02:26:00 +02:00
|
|
|
|
|
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PM: Document rules on using pm_runtime_resume() in system suspend callbacks
It quite often is necessary to resume devices from runtime suspend
during system suspend for various reasons (for example, if their
wakeup settings need to be changed), but that requires middle-layer
or subsystem code to follow additional rules which currently are not
clearly documented.
Namely, if a driver calls pm_runtime_resume() for the device from
its ->suspend (or equivalent) system sleep callback, that may not
work if the middle layer above it has updated the state of the
device from its ->prepare or ->suspend callbacks already in an
incompatible way. For this reason, all middle layers must follow
the rule that, until the ->suspend callback provided by the device's
driver is invoked, the only way in which the device's state can be
updated is by calling pm_runtime_resume() for it, if necessary.
Fortunately enough, all middle layers in the code base today follow
this rule, but it is not explicitly stated anywhere, so do that.
Note that calling pm_runtime_resume() from the ->suspend callback
of a driver will cause the ->runtime_resume callback provided by the
middle layer to be invoked, but the rule above guarantees that this
callback will nest properly with the middle layer's ->suspend
callback and it will play well with the ->prepare one invoked before.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
2017-09-20 02:26:00 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-18 18:55:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-26 12:12:08 +02:00
|
|
|
|
|
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-18 18:55:32 +02:00
|
|
|
|
|
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
2017-10-26 12:12:08 +02:00
|
|
|
|
|
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-18 18:55:32 +02:00
|
|
|
|
|
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-18 18:55:32 +02:00
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-18 18:55:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-10-26 12:12:08 +02:00
|
|
|
|
2011-07-01 22:29:05 +02:00
|
|
|
|
2021-06-16 08:27:16 +02:00
|
|
|
|
2017-11-18 15:31:49 +01:00
|
|
|
|
2017-02-02 01:32:13 +01:00
|
|
|
|
2020-04-18 18:55:32 +02:00
|
|
|
|
|
|
|
|
|
2017-11-18 15:31:49 +01:00
|
|
|
|
2020-04-18 18:55:32 +02:00
|
|
|
|
2017-11-18 15:31:49 +01:00
|
|
|
|
2020-04-18 18:55:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-12-10 01:02:13 +01:00
|
|
|
|
2020-04-18 18:55:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
2020-04-18 18:55:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2020-04-25 16:35:40 -04:00
|
|
|
|
|
|
|
|
|
2020-04-18 18:55:32 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|