diff options
| author | Fernando Guzman Lugo <fernando.lugo@ti.com> | 2011-06-08 19:06:50 -0500 |
|---|---|---|
| committer | Iliyan Malchev <malchev@google.com> | 2011-07-08 16:16:54 -0700 |
| commit | 531d334239ae88af53c85ea00853f1cb0ec49dda (patch) | |
| tree | 5e6a1110b4d89b030e63d78e0b87cfbe7fc736ef /.gitignore | |
| parent | cd6577880568e02b3e343955cf771fd6e76735f2 (diff) | |
| download | kernel_samsung_tuna-531d334239ae88af53c85ea00853f1cb0ec49dda.zip kernel_samsung_tuna-531d334239ae88af53c85ea00853f1cb0ec49dda.tar.gz kernel_samsung_tuna-531d334239ae88af53c85ea00853f1cb0ec49dda.tar.bz2 | |
remoteproc: add runtime PM autosuspend support
Going to suspend and resuming is a heavy task with much latency. For that
reason remoteproc should go to suspend after some time of inactivity. However,
the remoteproc driver cannot know by itself if activity is being performing on
the remote processor (the driver is only in charge of turning it on/off). That
is why remoteproc adds new APIs to be notified when the remote processor is
used and then restart suspend timeout.
Remote proc users need to use these new APIs. Besides, if they have issues when
the remote processor goes to suspend without their knowledge, they need to
register for suspend/resume notifications. Returning an error in the
notification callback means they are using the remote processor and the
autosuspend should be cancelled.
Signed-off-by: Fernando Guzman Lugo <fernando.lugo@ti.com>
Signed-off-by: Iliyan Malchev <malchev@google.com>
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions