linux-remoteproc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Arnaud POULIQUEN <arnaud.pouliquen@st.com>
Cc: "ohad@wizery.com" <ohad@wizery.com>,
	"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
	Loic PALLARDY <loic.pallardy@st.com>,
	"mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>,
	Alexandre TORGUE <alexandre.torgue@st.com>,
	"linux-remoteproc@vger.kernel.org"
	<linux-remoteproc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-stm32@st-md-mailman.stormreply.com" 
	<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH v6 00/11] remoteproc: stm32: Add support for attaching to M4
Date: Wed, 15 Jul 2020 09:32:53 -0600	[thread overview]
Message-ID: <CANLsYkyWLowSk1Zq7oWUzgsF=7FDVwe6XDgA6foWyX0VQwTE4g@mail.gmail.com> (raw)
In-Reply-To: <1cde5c1d5d9047149c93e031c5093492@SFHDAG3NODE1.st.com>

On Wed, 15 Jul 2020 at 00:51, Arnaud POULIQUEN <arnaud.pouliquen@st.com> wrote:
>
> Hi Mathieu
>
> > -----Original Message-----
> > From: Mathieu Poirier <mathieu.poirier@linaro.org>
> > Sent: mardi 14 juillet 2020 22:05
> > To: ohad@wizery.com; bjorn.andersson@linaro.org; Loic PALLARDY
> > <loic.pallardy@st.com>; Arnaud POULIQUEN <arnaud.pouliquen@st.com>;
> > mcoquelin.stm32@gmail.com; Alexandre TORGUE
> > <alexandre.torgue@st.com>
> > Cc: linux-remoteproc@vger.kernel.org; linux-kernel@vger.kernel.org; linux-
> > stm32@st-md-mailman.stormreply.com
> > Subject: [PATCH v6 00/11] remoteproc: stm32: Add support for attaching to
> > M4
> >
> > This set applies on top of [1] and refactors the STM32 platform code in order
> > to attach to the M4 remote processor when it has been started by the boot
> > loader.
> >
> > New to V6:
> > 1) Removed extra newline in patch 06.
> > 2) Re-worked title and changelog of patch 08 to better reflect
> >    what is done by the patch.
> >
> > Tested on ST's mp157c development board.
>
> I don' t know if you don't see  it on last  version or if you prefer that I review your update first... so for the series

Ah yes, my apologies on that - I misread the comment you left me in
00/11 of the V5 set.

>
> Acked-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>
>
> Thanks,
> Arnaud
>
> >
> > Thanks,
> > Mathieu
> >
> > [1].https://patchwork.kernel.org/project/linux-
> > remoteproc/list/?series=318275
> >
> > Mathieu Poirier (11):
> >   remoteproc: stm32: Decouple rproc from memory translation
> >   remoteproc: stm32: Request IRQ with platform device
> >   remoteproc: stm32: Decouple rproc from DT parsing
> >   remoteproc: stm32: Remove memory translation from DT parsing
> >   remoteproc: stm32: Parse syscon that will manage M4 synchronisation
> >   remoteproc: stm32: Properly set co-processor state when attaching
> >   remoteproc: Make function rproc_resource_cleanup() public
> >   remoteproc: stm32: Parse memory regions when attaching to M4
> >   remoteproc: stm32: Properly handle the resource table when attaching
> >   remoteproc: stm32: Introduce new attach() operation
> >   remoteproc: stm32: Update M4 state in stm32_rproc_stop()
> >
> >  drivers/remoteproc/remoteproc_core.c |   3 +-
> >  drivers/remoteproc/stm32_rproc.c     | 214 ++++++++++++++++++++++++--
> > -
> >  include/linux/remoteproc.h           |   1 +
> >  3 files changed, 198 insertions(+), 20 deletions(-)
> >
> > --
> > 2.25.1
>

  reply	other threads:[~2020-07-15 15:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14 20:04 [PATCH v6 00/11] remoteproc: stm32: Add support for attaching to M4 Mathieu Poirier
2020-07-14 20:04 ` [PATCH v6 01/11] remoteproc: stm32: Decouple rproc from memory translation Mathieu Poirier
2020-07-14 20:04 ` [PATCH v6 02/11] remoteproc: stm32: Request IRQ with platform device Mathieu Poirier
2020-07-14 20:04 ` [PATCH v6 03/11] remoteproc: stm32: Decouple rproc from DT parsing Mathieu Poirier
2020-07-14 20:04 ` [PATCH v6 04/11] remoteproc: stm32: Remove memory translation " Mathieu Poirier
2020-07-14 20:04 ` [PATCH v6 05/11] remoteproc: stm32: Parse syscon that will manage M4 synchronisation Mathieu Poirier
2020-07-14 20:04 ` [PATCH v6 06/11] remoteproc: stm32: Properly set co-processor state when attaching Mathieu Poirier
2020-07-14 20:04 ` [PATCH v6 07/11] remoteproc: Make function rproc_resource_cleanup() public Mathieu Poirier
2020-07-14 20:04 ` [PATCH v6 08/11] remoteproc: stm32: Parse memory regions when attaching to M4 Mathieu Poirier
2020-07-14 20:04 ` [PATCH v6 09/11] remoteproc: stm32: Properly handle the resource table when attaching Mathieu Poirier
2020-07-14 20:04 ` [PATCH v6 10/11] remoteproc: stm32: Introduce new attach() operation Mathieu Poirier
2020-07-14 20:04 ` [PATCH v6 11/11] remoteproc: stm32: Update M4 state in stm32_rproc_stop() Mathieu Poirier
2020-07-15  6:51 ` [PATCH v6 00/11] remoteproc: stm32: Add support for attaching to M4 Arnaud POULIQUEN
2020-07-15 15:32   ` Mathieu Poirier [this message]
2020-07-22  0:00 ` patchwork-bot+linux-remoteproc

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='CANLsYkyWLowSk1Zq7oWUzgsF=7FDVwe6XDgA6foWyX0VQwTE4g@mail.gmail.com' \
    --to=mathieu.poirier@linaro.org \
    --cc=alexandre.torgue@st.com \
    --cc=arnaud.pouliquen@st.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=loic.pallardy@st.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=ohad@wizery.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).