Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH 0/2] TI K3 R5F remoteproc support on AM46x SoCs
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>
References: <20210318215842.8196-1-s-anna@ti.com>
From:   Suman Anna <s-anna@ti.com>
Message-ID: <1759c728-6d13-ce5b-e052-681d437b55ad@ti.com>
Date:   Thu, 18 Mar 2021 17:07:12 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <20210318215842.8196-1-s-anna@ti.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

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(-)
>