From: Rob Herring <robh@kernel.org>
To: Suman Anna <s-anna@ti.com>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
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 v4 0/4] TI K3 R5F remoteproc support
Date: Tue, 22 Sep 2020 13:47:53 -0600 [thread overview]
Message-ID: <20200922194753.GA3105316@bogus> (raw)
In-Reply-To: <20200908174556.21277-1-s-anna@ti.com>
On Tue, Sep 08, 2020 at 12:45:52PM -0500, Suman Anna wrote:
> Hi All,
>
> The following is v4 of the TI K3 R5F remoteproc driver series supporting all
> the R5F processor clusters/subsystems on TI AM65x and J721E SoCs. Please
> see the v1 cover-letter [1] for the features supported on these R5F processors.
>
> This series is a rebased version on top of the latest v5.9-rc baseline and
> includes very minor fixes w.r.t v3. The previous K3 DSP dependencies are now
> available in mainline kernel. Please see the individual patches for the delta
> differences (Only patches 1 and 2 updated).
>
> Bjorn,
> This series is only waiting on bindings ack and the conclusion on the bindings
> discussion from v2 [4] on which I haven't seen any forward progress on this
> despite all the clarifications. I do not expect any changes even w.r.t System DT,
> and we can't really have a common binding between TI and Xilinx R5Fs.
Why not? I'm pretty sure lockstep or not is a thing for both and TCMs
seem to be a common thing.
And I don't really think System DT will not impact it. Though it's not
well enough defined to say either way IMO.
But if Bjorn wants to take this, fine. I'm not acking it though nor
worrying about it for any compatibility with system DT.
Rob
next prev parent reply other threads:[~2020-09-22 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 17:45 [PATCH v4 0/4] TI K3 R5F remoteproc support Suman Anna
2020-09-08 17:45 ` [PATCH v4 1/4] dt-bindings: remoteproc: Add bindings for R5F subsystem on TI K3 SoCs Suman Anna
2020-09-08 17:45 ` [PATCH v4 2/4] remoteproc: k3-r5: Add a remoteproc driver for R5F subsystem Suman Anna
2020-09-08 17:45 ` [PATCH v4 3/4] remoteproc: k3-r5: Initialize TCM memories for ECC Suman Anna
2020-09-08 17:45 ` [PATCH v4 4/4] remoteproc: k3-r5: Add loading support for on-chip SRAM regions Suman Anna
2020-09-22 19:47 ` Rob Herring [this message]
2020-09-22 20:26 ` [PATCH v4 0/4] TI K3 R5F remoteproc support Suman Anna
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=20200922194753.GA3105316@bogus \
--to=robh@kernel.org \
--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=s-anna@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 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).