From: Suman Anna <s-anna@ti.com> To: Bjorn Andersson <bjorn.andersson@linaro.org>, Mathieu Poirier <mathieu.poirier@linaro.org>, Rob Herring <robh+dt@kernel.org> Cc: Lokesh Vutla <lokeshvutla@ti.com>, <linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>, Suman Anna <s-anna@ti.com> Subject: [PATCH 0/3] TI K3 R5F remoteproc support on J7200 SoCs Date: Wed, 18 Nov 2020 19:05:28 -0600 [thread overview] Message-ID: <20201119010531.21083-1-s-anna@ti.com> (raw) Hi All, The following series enhances the K3 R5F remoteproc driver to add support for the R5F clusters on the newer TI K3 J7200 SoC family. The J7200 SoCs have 2 R5FSS clusters, and both clusters are capable of supporting either the LockStep or Split-modes like on the existing AM65x and J721E SoCs. The R5FSS IP though is revised compared to K3 AM65x and J721E SoCs and has two new features: 1. TCMs are auto-initialized during module power-up, and the behavior is programmable through a SEC_MMR register bit. 2. The LockStep-mode allows the Core1 TCMs to be combined with the Core0 TCMs effectively doubling the amount of TCMs available. The LockStep-mode on previous SoCs could only use the Core0 TCMs. This combined TCMs appear contiguous at the respective Core0 TCM addresses. The series is based on 5.10-rc1, and can apply on top of the current rproc-next branch as well. Following is the patch summary: - Patch 1 updates the dt-bindings - Patch 2 introduces new SoC data logic and handles the TCM auto-init feature - Patch 3 handles the TCM adjustment logic in Split-mode regards Suman Suman Anna (3): dt-bindings: remoteproc: k3-r5f: Update bindings for J7200 SoCs remoteproc: k3-r5: Extend support to R5F clusters on J7200 SoCs remoteproc: k3-r5: Adjust TCM sizes in Split-mode on J7200 SoCs .../bindings/remoteproc/ti,k3-r5f-rproc.yaml | 2 + drivers/remoteproc/ti_k3_r5_remoteproc.c | 95 ++++++++++++++++++- 2 files changed, 95 insertions(+), 2 deletions(-) -- 2.28.0
WARNING: multiple messages have this Message-ID (diff)
From: Suman Anna <s-anna@ti.com> To: Bjorn Andersson <bjorn.andersson@linaro.org>, Mathieu Poirier <mathieu.poirier@linaro.org>, Rob Herring <robh+dt@kernel.org> Cc: devicetree@vger.kernel.org, Lokesh Vutla <lokeshvutla@ti.com>, linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH 0/3] TI K3 R5F remoteproc support on J7200 SoCs Date: Wed, 18 Nov 2020 19:05:28 -0600 [thread overview] Message-ID: <20201119010531.21083-1-s-anna@ti.com> (raw) Hi All, The following series enhances the K3 R5F remoteproc driver to add support for the R5F clusters on the newer TI K3 J7200 SoC family. The J7200 SoCs have 2 R5FSS clusters, and both clusters are capable of supporting either the LockStep or Split-modes like on the existing AM65x and J721E SoCs. The R5FSS IP though is revised compared to K3 AM65x and J721E SoCs and has two new features: 1. TCMs are auto-initialized during module power-up, and the behavior is programmable through a SEC_MMR register bit. 2. The LockStep-mode allows the Core1 TCMs to be combined with the Core0 TCMs effectively doubling the amount of TCMs available. The LockStep-mode on previous SoCs could only use the Core0 TCMs. This combined TCMs appear contiguous at the respective Core0 TCM addresses. The series is based on 5.10-rc1, and can apply on top of the current rproc-next branch as well. Following is the patch summary: - Patch 1 updates the dt-bindings - Patch 2 introduces new SoC data logic and handles the TCM auto-init feature - Patch 3 handles the TCM adjustment logic in Split-mode regards Suman Suman Anna (3): dt-bindings: remoteproc: k3-r5f: Update bindings for J7200 SoCs remoteproc: k3-r5: Extend support to R5F clusters on J7200 SoCs remoteproc: k3-r5: Adjust TCM sizes in Split-mode on J7200 SoCs .../bindings/remoteproc/ti,k3-r5f-rproc.yaml | 2 + drivers/remoteproc/ti_k3_r5_remoteproc.c | 95 ++++++++++++++++++- 2 files changed, 95 insertions(+), 2 deletions(-) -- 2.28.0 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-11-19 1:05 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-19 1:05 Suman Anna [this message] 2020-11-19 1:05 ` [PATCH 0/3] TI K3 R5F remoteproc support on J7200 SoCs Suman Anna 2020-11-19 1:05 ` [PATCH 1/3] dt-bindings: remoteproc: k3-r5f: Update bindings for " Suman Anna 2020-11-19 1:05 ` Suman Anna 2020-11-19 1:05 ` [PATCH 2/3] remoteproc: k3-r5: Extend support to R5F clusters on " Suman Anna 2020-11-19 1:05 ` Suman Anna 2020-11-19 1:05 ` [PATCH 3/3] remoteproc: k3-r5: Adjust TCM sizes in Split-mode " Suman Anna 2020-11-19 1:05 ` Suman Anna 2020-11-23 23:51 ` Mathieu Poirier 2020-11-23 23:51 ` Mathieu Poirier 2020-11-24 0:55 ` Mathieu Poirier 2020-11-24 0:55 ` Mathieu Poirier 2020-11-30 15:47 ` Suman Anna 2020-11-30 15:47 ` Suman Anna 2020-11-26 17:40 ` [PATCH 0/3] TI K3 R5F remoteproc support " 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=20201119010531.21083-1-s-anna@ti.com \ --to=s-anna@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=lokeshvutla@ti.com \ --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.