diff options
author | Adrian Hunter <[email protected]> | 2011-10-03 15:33:33 +0300 |
---|---|---|
committer | Chris Ball <[email protected]> | 2011-10-26 16:32:19 -0400 |
commit | 08a7e1dfaa63bf5132b5b7231fcf9a33473c78f5 (patch) | |
tree | f52edc2a2dbca622d3e26836728bc9ffe4216fda /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 88b47679746b81534002bcba42da97ab82b5d12a (diff) |
mmc: core: move ->request() call from atomic context
mmc_request_done() is sometimes called from interrupt or other atomic
context. Mostly all mmc_request_done() does is complete(), however it
contains code to retry on error, which uses ->request(). As the error
path is certainly not performance critical, this may be moved to the
waiting function mmc_wait_for_req_done().
This allows ->request() to use runtime PM get_sync() and guarantee it
is never in an atomic context.
Signed-off-by: Adrian Hunter <[email protected]>
Acked-by: Ulf Hansson <[email protected]>
Signed-off-by: Chris Ball <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions