diff options
| author | Heiner Kallweit <[email protected]> | 2019-01-19 22:06:25 +0100 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2019-01-19 16:09:14 -0800 |
| commit | 58ba566ccbae0ec629ab9e36006d1b79765fe252 (patch) | |
| tree | 3fcc7928b2998df186c4daacd2582888d20d4e13 /scripts/gdb/linux/symbols.py | |
| parent | df320ed7b3e46c93a57eb77c71228415bcd5b8b8 (diff) | |
r8169: reset chip synchronously in __rtl8169_resume
Triggering an asynchronous reset is problematic for the following
reasons, therefore reset the chip synchronously.
- The reset routine resets registers and parameters behind our back
what may collide with code executed after triggering the reset.
- __rtl8169_resume() is called as part of pm_runtime_get_sync() and
callers expect that the chip is fully resumed afterwards.
In context of this driver triggering an asynchonous reset should be
considered an emergency procedure.
Signed-off-by: Heiner Kallweit <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/symbols.py')
0 files changed, 0 insertions, 0 deletions