diff options
| author | Stefan Agner <stefan@agner.ch> | 2015-05-18 12:33:27 -0400 |
|---|---|---|
| committer | Marc Kleine-Budde <mkl@pengutronix.de> | 2015-07-16 03:04:21 -0400 |
| commit | 25b401c1816ae64bcc5dcb1d39ab41812522a0ce (patch) | |
| tree | e2c2df8846c9b5bb0c6374b4194222f1fa68149a /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 15afb10df4a3f1bd781373ffd968e70cc4b21a42 (diff) | |
can: mcp251x: fix resume when device is down
If a valid power regulator or a dummy regulator is used (which
happens to be the case when no regulator is specified), restart_work
is queued no matter whether the device was running or not at suspend
time. Since work queues get initialized in the ndo_open callback,
resuming leads to a NULL pointer exception.
Reverse exactly the steps executed at suspend time:
- Enable the power regulator in any case
- Enable the transceiver regulator if the device was running, even in
case we have a power regulator
- Queue restart_work only in case the device was running
Fixes: bf66f3736a94 ("can: mcp251x: Move to threaded interrupts instead of workqueues.")
Signed-off-by: Stefan Agner <stefan@agner.ch>
Cc: linux-stable <stable@vger.kernel.org>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions