From: Hari Nagalla <hnagalla@ti.com> To: <bjorn.andersson@linaro.org>, <mathieu.poirier@linaro.org>, <robh+dt@kernel.org> Cc: <devicetree@vger.kernel.org>, <linux-remoteproc@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <hnagalla@ti.com> Subject: [PATCH 0/2] TI K3 M4F support on AM64x SoC Date: Sun, 9 Jan 2022 22:06:48 -0600 [thread overview] Message-ID: <20220110040650.18186-1-hnagalla@ti.com> (raw) Hi All, The following series introduces K3 M4F remoteproc driver support for AM64x SoC family. The AM64X SoCs has a ARM Cortex M4F core in 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 Regards Hari Hari Nagalla (2): dt-bindings: remoteproc: k3-m4f: Add bindings for K3 AM64x SoCs remoteproc: k4-m4: Add a remoteproc driver for M4F subsystem .../bindings/remoteproc/ti,k3-m4f-rproc.yaml | 121 +++ drivers/remoteproc/Kconfig | 13 + drivers/remoteproc/Makefile | 1 + drivers/remoteproc/ti_k3_m4_remoteproc.c | 899 ++++++++++++++++++ 4 files changed, 1034 insertions(+) create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml create mode 100644 drivers/remoteproc/ti_k3_m4_remoteproc.c -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Hari Nagalla <hnagalla@ti.com> To: <bjorn.andersson@linaro.org>, <mathieu.poirier@linaro.org>, <robh+dt@kernel.org> Cc: <devicetree@vger.kernel.org>, <linux-remoteproc@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <hnagalla@ti.com> Subject: [PATCH 0/2] TI K3 M4F support on AM64x SoC Date: Sun, 9 Jan 2022 22:06:48 -0600 [thread overview] Message-ID: <20220110040650.18186-1-hnagalla@ti.com> (raw) Hi All, The following series introduces K3 M4F remoteproc driver support for AM64x SoC family. The AM64X SoCs has a ARM Cortex M4F core in 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 Regards Hari Hari Nagalla (2): dt-bindings: remoteproc: k3-m4f: Add bindings for K3 AM64x SoCs remoteproc: k4-m4: Add a remoteproc driver for M4F subsystem .../bindings/remoteproc/ti,k3-m4f-rproc.yaml | 121 +++ drivers/remoteproc/Kconfig | 13 + drivers/remoteproc/Makefile | 1 + drivers/remoteproc/ti_k3_m4_remoteproc.c | 899 ++++++++++++++++++ 4 files changed, 1034 insertions(+) create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml create mode 100644 drivers/remoteproc/ti_k3_m4_remoteproc.c -- 2.17.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-01-10 4:07 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-10 4:06 Hari Nagalla [this message] 2022-01-10 4:06 ` [PATCH 0/2] TI K3 M4F support on AM64x SoC Hari Nagalla 2022-01-10 4:06 ` [PATCH 1/2] dt-bindings: remoteproc: k3-m4f: Add bindings for K3 AM64x SoCs Hari Nagalla 2022-01-10 4:06 ` Hari Nagalla 2022-01-10 16:48 ` Rob Herring 2022-01-10 16:48 ` Rob Herring 2022-01-31 17:19 ` Mathieu Poirier 2022-01-31 17:19 ` Mathieu Poirier 2022-01-10 4:06 ` [PATCH 2/2] remoteproc: k4-m4: Add a remoteproc driver for M4F subsystem Hari Nagalla 2022-01-10 4:06 ` Hari Nagalla 2022-01-31 18:27 ` Mathieu Poirier 2022-01-31 18:27 ` Mathieu Poirier 2022-01-31 18:36 ` Mathieu Poirier 2022-01-31 18:36 ` Mathieu Poirier
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=20220110040650.18186-1-hnagalla@ti.com \ --to=hnagalla@ti.com \ --cc=bjorn.andersson@linaro.org \ --cc=devicetree@vger.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=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: linkBe 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.