Linux-remoteproc Archive mirror
 help / color / mirror / Atom feed
From: Wadim Egorov <w.egorov@phytec.de>
To: Andrew Davis <afd@ti.com>, Bjorn Andersson <andersson@kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Nishanth Menon <nm@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Hari Nagalla <hnagalla@ti.com>
Cc: <linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v11 0/9] TI K3 M4F support on AM62 and AM64 SoCs
Date: Mon, 19 Aug 2024 10:33:38 +0200	[thread overview]
Message-ID: <04bba41d-7e7f-4c3f-9f92-1b4165968c12@phytec.de> (raw)
In-Reply-To: <20240802152109.137243-1-afd@ti.com>



Am 02.08.24 um 17:21 schrieb Andrew Davis:
> Hello all,
> 
> This is the continuation of the M4F RProc support series from here[0].
> I'm helping out with the upstream task for Hari and so versions (v8+)
> is a little different than the previous(v7-) postings[0]. Most notable
> change I've introduced being the patches factoring out common support
> from the current K3 R5 and DSP drivers have been dropped. I'd like
> to do that re-factor *after* getting this driver in shape, that way
> we have 3 similar drivers to factor out from vs trying to make those
> changes in parallel with the series adding M4 support.
> 
> Anyway, details on our M4F subsystem can be found the
> the AM62 TRM in the section on the same:
> 
> AM62x Technical Reference Manual (SPRUIV7A – MAY 2022)
> https://www.ti.com/lit/pdf/SPRUIV7A
> 
> Thanks,
> Andrew
> 
> [0] https://lore.kernel.org/linux-arm-kernel/20240202175538.1705-5-hnagalla@ti.com/T/
> 
> Changes for v11:
>   - Added patch [2/9] factoring out a common function
>   - Addressed comments by Mathieu from v10
>   - Rebased on v6.11-rc1
>   - Small reworks in driver for readability

Tested on a AM62x & AM64x using phycore-am62x & phycore-am64x, so

Tested-by: Wadim Egorov <w.egorov@phytec.de>

> 
> Changes for v10:
>   - Rebased on v6.10-rc3
>   - Added AM64 M4 support in DT
>   - Addressed comments by Mathieu from v9
> 
> Changes for v9:
>   - Fixed reserved-memory.yaml text in [1/5]
>   - Split dts patch into one for SoC and one for board enable
>   - Corrected DT property order and formatting [4/5][5/5]
> 
> Andrew Davis (1):
>    remoteproc: k3: Factor out TI-SCI processor control OF get function
> 
> Hari Nagalla (7):
>    dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs
>    arm64: dts: ti: k3-am62: Add M4F remoteproc node
>    arm64: dts: ti: k3-am625-sk: Add M4F remoteproc node
>    arm64: dts: ti: k3-am64: Add M4F remoteproc node
>    arm64: dts: ti: k3-am642-sk: Add M4F remoteproc node
>    arm64: dts: ti: k3-am642-evm: Add M4F remoteproc node
>    arm64: defconfig: Enable TI K3 M4 remoteproc driver
> 
> Martyn Welch (1):
>    remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem
> 
>   .../bindings/remoteproc/ti,k3-m4f-rproc.yaml  | 125 ++++
>   arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi       |  13 +
>   .../arm64/boot/dts/ti/k3-am62x-sk-common.dtsi |  19 +
>   arch/arm64/boot/dts/ti/k3-am64-mcu.dtsi       |  13 +
>   arch/arm64/boot/dts/ti/k3-am642-evm.dts       |  19 +
>   arch/arm64/boot/dts/ti/k3-am642-sk.dts        |  19 +
>   arch/arm64/configs/defconfig                  |   1 +
>   drivers/remoteproc/Kconfig                    |  13 +
>   drivers/remoteproc/Makefile                   |   1 +
>   drivers/remoteproc/ti_k3_dsp_remoteproc.c     |  28 +-
>   drivers/remoteproc/ti_k3_m4_remoteproc.c      | 667 ++++++++++++++++++
>   drivers/remoteproc/ti_k3_r5_remoteproc.c      |  28 +-
>   drivers/remoteproc/ti_sci_proc.h              |  26 +
>   13 files changed, 918 insertions(+), 54 deletions(-)
>   create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml
>   create mode 100644 drivers/remoteproc/ti_k3_m4_remoteproc.c
> 


  parent reply	other threads:[~2024-08-19  8:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 15:21 [PATCH v11 0/9] TI K3 M4F support on AM62 and AM64 SoCs Andrew Davis
2024-08-02 15:21 ` [PATCH v11 1/9] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs Andrew Davis
2024-08-02 15:21 ` [PATCH v11 2/9] remoteproc: k3: Factor out TI-SCI processor control OF get function Andrew Davis
2024-08-19  8:49   ` Wadim Egorov
2024-08-02 15:21 ` [PATCH v11 3/9] remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem Andrew Davis
2024-08-15 16:46   ` Mathieu Poirier
2024-08-16 14:36     ` Mathieu Poirier
2024-08-19  8:32       ` Vignesh Raghavendra
2024-08-19 15:32         ` Mathieu Poirier
2024-08-19 15:39           ` Krzysztof Kozlowski
2024-08-19 15:54             ` Andrew Davis
2024-08-21 17:12               ` Mathieu Poirier
2024-08-19  8:47   ` Wadim Egorov
2024-08-02 15:21 ` [PATCH v11 4/9] arm64: dts: ti: k3-am62: Add M4F remoteproc node Andrew Davis
2024-08-19  8:48   ` Wadim Egorov
2024-08-02 15:21 ` [PATCH v11 5/9] arm64: dts: ti: k3-am625-sk: " Andrew Davis
2024-08-02 15:21 ` [PATCH v11 6/9] arm64: dts: ti: k3-am64: " Andrew Davis
2024-08-02 15:21 ` [PATCH v11 7/9] arm64: dts: ti: k3-am642-sk: " Andrew Davis
2024-08-02 15:21 ` [PATCH v11 8/9] arm64: dts: ti: k3-am642-evm: " Andrew Davis
2024-08-02 15:21 ` [PATCH v11 9/9] arm64: defconfig: Enable TI K3 M4 remoteproc driver Andrew Davis
2025-01-08  7:31   ` Daniel Schultz
2024-08-19  8:33 ` Wadim Egorov [this message]
2025-01-08 15:49 ` (subset) [PATCH v11 0/9] TI K3 M4F support on AM62 and AM64 SoCs Nishanth Menon

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=04bba41d-7e7f-4c3f-9f92-1b4165968c12@phytec.de \
    --to=w.egorov@phytec.de \
    --cc=afd@ti.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hnagalla@ti.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=nm@ti.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=vigneshr@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 read-only IMAP folder(s) and NNTP newsgroup(s).