From: Alexandre Torgue <alexandre.torgue@st.com>
To: Fabien Dessenne <fabien.dessenne@st.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org
Cc: Loic Pallardy <loic.pallardy@st.com>,
Arnaud Pouliquen <arnaud.pouliquen@st.com>,
Ludovic Barre <ludovic.barre@st.com>,
Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: Re: [PATCH 0/8] stm32 m4 remoteproc on STM32MP157c
Date: Tue, 26 Mar 2019 11:37:11 +0100 [thread overview]
Message-ID: <695af4c3-b3fe-183f-02c7-fd080048b29c@st.com> (raw)
In-Reply-To: <1551795849-13672-1-git-send-email-fabien.dessenne@st.com>
Hi fabien
On 3/5/19 3:24 PM, Fabien Dessenne wrote:
> STMicrolectronics STM32MP157 MPU are based on a Dual Arm Cortex-A7 core and a
> Cortex-M4.
> This patchset adds the support of the stm32_rproc driver allowing to control
> the M4 remote processor.
>
> Fabien Dessenne (8):
> dt-bindings: stm32: add bindings for ML-AHB interconnect
> dt-bindings: remoteproc: add bindings for stm32 remote processor
> driver
> remoteproc: stm32: add an ST stm32_rproc driver
> ARM: dts: stm32: add m4 remoteproc support on STM32MP157c
> ARM: dts: stm32: declare copro reserved memories on STM32MP157c-ed1
> ARM: dts: stm32: enable m4 coprocessor support on STM32MP157c-ed1
> ARM: dts: stm32: declare copro reserved memories on STM32MP157a-dk1
> ARM: dts: stm32: enable m4 coprocessor support on STM32MP157a-dk1
>
> .../devicetree/bindings/arm/stm32/mlahb.txt | 30 +
> .../devicetree/bindings/remoteproc/stm32-rproc.txt | 67 +++
> arch/arm/boot/dts/stm32mp157a-dk1.dts | 54 ++
> arch/arm/boot/dts/stm32mp157c-ed1.dts | 54 ++
> arch/arm/boot/dts/stm32mp157c.dtsi | 21 +
> drivers/remoteproc/Kconfig | 15 +
> drivers/remoteproc/Makefile | 1 +
> drivers/remoteproc/stm32_rproc.c | 624 +++++++++++++++++++++
> 8 files changed, 866 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/stm32/mlahb.txt
> create mode 100644 Documentation/devicetree/bindings/remoteproc/stm32-rproc.txt
> create mode 100644 drivers/remoteproc/stm32_rproc.c
>
Concerning DT patches, at first glance I don't see obvious issues. I'll
take Dt patches as soon as driver and bindings patches are acked.
regards
Alex
prev parent reply other threads:[~2019-03-26 10:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 14:24 [PATCH 0/8] stm32 m4 remoteproc on STM32MP157c Fabien Dessenne
2019-03-05 14:24 ` [PATCH 1/8] dt-bindings: stm32: add bindings for ML-AHB interconnect Fabien Dessenne
2019-03-27 23:07 ` Rob Herring
2019-03-29 15:59 ` Fabien DESSENNE
2019-04-04 1:29 ` Rob Herring
2019-03-05 14:24 ` [PATCH 2/8] dt-bindings: remoteproc: add bindings for stm32 remote processor driver Fabien Dessenne
2019-03-27 23:23 ` Rob Herring
2019-03-05 14:24 ` [PATCH 3/8] remoteproc: stm32: add an ST stm32_rproc driver Fabien Dessenne
2019-03-05 14:24 ` [PATCH 4/8] ARM: dts: stm32: add m4 remoteproc support on STM32MP157c Fabien Dessenne
2019-03-05 14:24 ` [PATCH 5/8] ARM: dts: stm32: declare copro reserved memories on STM32MP157c-ed1 Fabien Dessenne
2019-03-05 14:24 ` [PATCH 6/8] ARM: dts: stm32: enable m4 coprocessor support " Fabien Dessenne
2019-03-05 14:24 ` [PATCH 7/8] ARM: dts: stm32: declare copro reserved memories on STM32MP157a-dk1 Fabien Dessenne
2019-03-05 14:24 ` [PATCH 8/8] ARM: dts: stm32: enable m4 coprocessor support " Fabien Dessenne
2019-03-26 10:37 ` Alexandre Torgue [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=695af4c3-b3fe-183f-02c7-fd080048b29c@st.com \
--to=alexandre.torgue@st.com \
--cc=arnaud.pouliquen@st.com \
--cc=benjamin.gaignard@st.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=fabien.dessenne@st.com \
--cc=linux-arm-kernel@lists.infradead.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=ludovic.barre@st.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.org \
/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).