All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hari Nagalla <hnagalla@ti.com>
To: <andersson@kernel.org>, <mathieu.poirier@linaro.org>,
	<p.zabel@pengutronix.de>, <martyn.welch@collabora.com>,
	<nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
	<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
	<conor+dt@kernel.org>
Cc: <linux-remoteproc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>
Subject: [PATCH v7 0/5] TI K3 M4F support on AM64x and AM62x SoCs
Date: Fri, 2 Feb 2024 11:55:33 -0600	[thread overview]
Message-ID: <20240202175538.1705-1-hnagalla@ti.com> (raw)

The following series introduces K3 M4F remoteproc driver support for
AM64x and AM62x SoC families. These SoCs have a ARM Cortex M4F core in
the MCU voltage domain. For safety oriented applications, this core is
operated independently with out any IPC to other cores on the SoC.
However, for non safety applications, some customers use it as a remote
processor and so linux remote proc support is extended to the M4F core.

See AM64x Technical Reference Manual (SPRUIM2C – SEPTEMBER 2021) for
further details: https://www.ti.com/lit/pdf/SPRUIM2

See AM62x Technical Reference Manual (SPRUIV7A – MAY 2022) for
further details: https://www.ti.com/lit/pdf/SPRUIV7A

kernel build log: https://paste.sr.ht/~hnagalla/be9d1c45e176ea8fa274ab13a3da43a9853fcf7f
dt-binding-check log: https://paste.sr.ht/~hnagalla/25912c85f6a8c68e3da24053fc060f38024fb8ab 
kernel boot log: https://paste.sr.ht/~hnagalla/5ba77847343f22b5f9ec2b7aeabc410aaf8cdf45

Hari Nagalla (2):
  dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs
  arm64: defconfig: Enable TI K3 M4 remote proc driver

Martyn Welch (3):
  remoteproc: k3: Move out data structures common with M4 driver
  remoteproc: k3: Move out functions common with M4 driver
  remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem

 .../bindings/remoteproc/ti,k3-m4f-rproc.yaml  |  138 ++
 arch/arm64/configs/defconfig                  |    1 +
 drivers/remoteproc/Kconfig                    |   13 +
 drivers/remoteproc/Makefile                   |    3 +-
 drivers/remoteproc/ti_k3_common.c             |  583 ++++++++
 drivers/remoteproc/ti_k3_common.h             |  107 ++
 drivers/remoteproc/ti_k3_dsp_remoteproc.c     | 1277 +++++------------
 drivers/remoteproc/ti_k3_m4_remoteproc.c      |  327 +++++
 8 files changed, 1539 insertions(+), 910 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml
 create mode 100644 drivers/remoteproc/ti_k3_common.c
 create mode 100644 drivers/remoteproc/ti_k3_common.h
 rewrite drivers/remoteproc/ti_k3_dsp_remoteproc.c (67%)
 create mode 100644 drivers/remoteproc/ti_k3_m4_remoteproc.c

-- 
2.34.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Hari Nagalla <hnagalla@ti.com>
To: <andersson@kernel.org>, <mathieu.poirier@linaro.org>,
	<p.zabel@pengutronix.de>, <martyn.welch@collabora.com>,
	<nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
	<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
	<conor+dt@kernel.org>
Cc: <linux-remoteproc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>
Subject: [PATCH v7 0/5] TI K3 M4F support on AM64x and AM62x SoCs
Date: Fri, 2 Feb 2024 11:55:33 -0600	[thread overview]
Message-ID: <20240202175538.1705-1-hnagalla@ti.com> (raw)

The following series introduces K3 M4F remoteproc driver support for
AM64x and AM62x SoC families. These SoCs have a ARM Cortex M4F core in
the MCU voltage domain. For safety oriented applications, this core is
operated independently with out any IPC to other cores on the SoC.
However, for non safety applications, some customers use it as a remote
processor and so linux remote proc support is extended to the M4F core.

See AM64x Technical Reference Manual (SPRUIM2C – SEPTEMBER 2021) for
further details: https://www.ti.com/lit/pdf/SPRUIM2

See AM62x Technical Reference Manual (SPRUIV7A – MAY 2022) for
further details: https://www.ti.com/lit/pdf/SPRUIV7A

kernel build log: https://paste.sr.ht/~hnagalla/be9d1c45e176ea8fa274ab13a3da43a9853fcf7f
dt-binding-check log: https://paste.sr.ht/~hnagalla/25912c85f6a8c68e3da24053fc060f38024fb8ab 
kernel boot log: https://paste.sr.ht/~hnagalla/5ba77847343f22b5f9ec2b7aeabc410aaf8cdf45

Hari Nagalla (2):
  dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs
  arm64: defconfig: Enable TI K3 M4 remote proc driver

Martyn Welch (3):
  remoteproc: k3: Move out data structures common with M4 driver
  remoteproc: k3: Move out functions common with M4 driver
  remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem

 .../bindings/remoteproc/ti,k3-m4f-rproc.yaml  |  138 ++
 arch/arm64/configs/defconfig                  |    1 +
 drivers/remoteproc/Kconfig                    |   13 +
 drivers/remoteproc/Makefile                   |    3 +-
 drivers/remoteproc/ti_k3_common.c             |  583 ++++++++
 drivers/remoteproc/ti_k3_common.h             |  107 ++
 drivers/remoteproc/ti_k3_dsp_remoteproc.c     | 1277 +++++------------
 drivers/remoteproc/ti_k3_m4_remoteproc.c      |  327 +++++
 8 files changed, 1539 insertions(+), 910 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml
 create mode 100644 drivers/remoteproc/ti_k3_common.c
 create mode 100644 drivers/remoteproc/ti_k3_common.h
 rewrite drivers/remoteproc/ti_k3_dsp_remoteproc.c (67%)
 create mode 100644 drivers/remoteproc/ti_k3_m4_remoteproc.c

-- 
2.34.1


             reply	other threads:[~2024-02-02 17:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 17:55 Hari Nagalla [this message]
2024-02-02 17:55 ` [PATCH v7 0/5] TI K3 M4F support on AM64x and AM62x SoCs Hari Nagalla
2024-02-02 17:55 ` [PATCH v7 1/5] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs Hari Nagalla
2024-02-02 17:55   ` Hari Nagalla
2024-02-02 19:15   ` Rob Herring
2024-02-02 19:15     ` Rob Herring
2024-02-02 21:50   ` Rob Herring
2024-02-02 21:50     ` Rob Herring
2024-02-02 17:55 ` [PATCH v7 2/5] remoteproc: k3: Move out data structures common with M4 driver Hari Nagalla
2024-02-02 17:55   ` Hari Nagalla
2024-02-05 22:36   ` Andrew Davis
2024-02-05 22:36     ` Andrew Davis
2024-02-02 17:55 ` [PATCH v7 3/5] remoteproc: k3: Move out functions " Hari Nagalla
2024-02-02 17:55   ` Hari Nagalla
2024-02-05 22:46   ` Andrew Davis
2024-02-05 22:46     ` Andrew Davis
2024-02-02 17:55 ` [PATCH v7 4/5] remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem Hari Nagalla
2024-02-02 17:55   ` Hari Nagalla
2024-02-02 17:55 ` [PATCH v7 5/5] arm64: defconfig: Enable TI K3 M4 remote proc driver Hari Nagalla
2024-02-02 17:55   ` Hari Nagalla

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=20240202175538.1705-1-hnagalla@ti.com \
    --to=hnagalla@ti.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=martyn.welch@collabora.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=nm@ti.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.