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>
Subject: Re: [PATCH 0/2] TI K3 R5F remoteproc support on AM46x SoCs
Date: Thu, 18 Mar 2021 17:07:12 -0500 [thread overview]
Message-ID: <1759c728-6d13-ce5b-e052-681d437b55ad@ti.com> (raw)
In-Reply-To: <20210318215842.8196-1-s-anna@ti.com>
On 3/18/21 4:58 PM, Suman Anna wrote:
> Hi All,
>
> The following series enhances the K3 R5F remoteproc driver to add support
> for the R5F clusters on the newer TI K3 AM64x SoC family. The AM64x SoCs
> have 2 R5FSS clusters and no DSPs. Both clusters are capable of supporting
> either the conventional Split-mode or a brand new "Single-CPU" mode.
>
> The revised R5FSS IP has the following unique features:
> 1. The new Single-CPU mode allows the Core1 TCMs to be combined with
> the Core0 TCMs effectively doubling the amount of TCMs available.
> This is same behavior as LockStep-mode on J7200 SoCs, but all other
> previous SoCs could only use the Core0 TCMs. This combined TCMs appear
> contiguous at the respective Core0 TCM addresses.
> 2. TCMs are auto-initialized during module power-up, and the behavior
> is programmable through a SEC_MMR register bit. This is same as on
> J7200 SoCs, and is not present on earlier AM65x and J721E SoCs.
>
> The series is based on 5.12-rc2, and can apply on top of the current
> rproc-next branch as well.
I had a small typo in the cover-letter subject line, should read "AM64x" instead
of "AM46x". Patches themselves use the correct term.
regards
Suman
>
> regards
> Suman
>
> Suman Anna (2):
> dt-bindings: remoteproc: k3-r5f: Update bindings for AM64x SoCs
> remoteproc: k3-r5: Extend support to R5F clusters on AM64x SoCs
>
> .../bindings/remoteproc/ti,k3-r5f-rproc.yaml | 31 +++-
> drivers/remoteproc/ti_k3_r5_remoteproc.c | 155 ++++++++++++++----
> 2 files changed, 152 insertions(+), 34 deletions(-)
>
prev parent reply other threads:[~2021-03-18 22:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 21:58 [PATCH 0/2] TI K3 R5F remoteproc support on AM46x SoCs Suman Anna
2021-03-18 21:58 ` [PATCH 1/2] dt-bindings: remoteproc: k3-r5f: Update bindings for AM64x SoCs Suman Anna
2021-03-18 21:58 ` [PATCH 2/2] remoteproc: k3-r5: Extend support to R5F clusters on " Suman Anna
2021-03-24 16:46 ` Mathieu Poirier
2021-03-24 17:29 ` Suman Anna
2021-03-25 17:30 ` Mathieu Poirier
2021-03-25 21:00 ` Suman Anna
2021-03-25 22:17 ` Mathieu Poirier
2021-03-26 14:50 ` Suman Anna
2021-03-18 22:07 ` Suman Anna [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=1759c728-6d13-ce5b-e052-681d437b55ad@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: 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).