From: Paul Cercueil <paul@crapouillou.net>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: ohad@wizery.com, bjorn.andersson@linaro.org, s-anna@ti.com,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] remoteproc: Address runtime PM issues
Date: Tue, 07 Jul 2020 12:49:27 +0200 [thread overview]
Message-ID: <F2I3DQ.SZMCCDC0DNAD3@crapouillou.net> (raw)
In-Reply-To: <20200630163118.3830422-1-mathieu.poirier@linaro.org>
Hi,
Le mar. 30 juin 2020 à 10:31, Mathieu Poirier
<mathieu.poirier@linaro.org> a écrit :
> This set follows the conversation that took place here[1] and provides
> the "two small patches" I alluded to at the end of the thread.
>
> Paul Cercueil: patch 1/2 is compile tested only - please see that it
> does what
> you want.
Still works fine, so
Tested-by: Paul Cercueil <paul@crapouillou.net>
for the patchset.
Cheers,
-Paul
> Suman Anna: Please test on your side and confirm that it addresses
> the Omap
> regression.
>
> Applies on top of rproc-next (7dcef3988eed)
>
> Thanks,
> Mathieu
>
> [1].
> https://lore.kernel.org/linux-remoteproc/20200515104340.10473-1-paul@crapouillou.net/T/#t
>
> Mathieu Poirier (2):
> remoteproc: ingenic: Move clock handling to prepare/unprepare
> callbacks
> Revert "remoteproc: Add support for runtime PM"
>
> drivers/remoteproc/ingenic_rproc.c | 84
> +++++++++-------------------
> drivers/remoteproc/remoteproc_core.c | 17 +-----
> 2 files changed, 27 insertions(+), 74 deletions(-)
>
> --
> 2.25.1
>
prev parent reply other threads:[~2020-07-07 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 16:31 [PATCH 0/2] remoteproc: Address runtime PM issues Mathieu Poirier
2020-06-30 16:31 ` [PATCH 1/2] remoteproc: ingenic: Move clock handling to prepare/unprepare callbacks Mathieu Poirier
2020-07-01 21:27 ` Suman Anna
2020-06-30 16:31 ` [PATCH 2/2] Revert "remoteproc: Add support for runtime PM" Mathieu Poirier
2020-07-01 21:21 ` Suman Anna
2020-07-01 21:28 ` [PATCH 0/2] remoteproc: Address runtime PM issues Suman Anna
2020-07-07 10:49 ` Paul Cercueil [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F2I3DQ.SZMCCDC0DNAD3@crapouillou.net \
--to=paul@crapouillou.net \
--cc=bjorn.andersson@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=ohad@wizery.com \
--cc=s-anna@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).