From: Rob Herring <robh@kernel.org>
To: Hari Nagalla <hnagalla@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
bjorn.andersson@linaro.org, linux-remoteproc@vger.kernel.org,
robh+dt@kernel.org, linux-kernel@vger.kernel.org,
mathieu.poirier@linaro.org, a-govindraju@ti.com
Subject: Re: [PATCH 2/4] dt-bindings: remoteproc: k3-dsp: Update bindings for J721S2 SoCs
Date: Tue, 30 Nov 2021 14:52:54 -0600 [thread overview]
Message-ID: <YaaPJrqtU7Ifoe8M@robh.at.kernel.org> (raw)
In-Reply-To: <20211122122726.8532-3-hnagalla@ti.com>
On Mon, 22 Nov 2021 06:27:24 -0600, Hari Nagalla wrote:
> The TI K3 J721S2 SoCs have two TMS320C71x DSP subsystems, and does not
> have any TMS320C66x DSP subsystems. The C71x DSP subsystem in J721S2
> SoCs is a similar to the C71x DSP on J721e with some minor core IP updates.
>
> Compatible info is updated for intuitvely matching to the new J721S2
> SoCs.
>
> Signed-off-by: Hari Nagalla <hnagalla@ti.com>
> ---
> .../devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-11-30 20:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 12:27 [PATCH 0/4] TI K3 R5F and C71x support on J721S2 Hari Nagalla
2021-11-22 12:27 ` [PATCH 1/4] dt-bindings: remoteproc: k3-r5f: Update bindings for J721S2 SoCs Hari Nagalla
2021-11-30 20:52 ` Rob Herring
2021-11-22 12:27 ` [PATCH 2/4] dt-bindings: remoteproc: k3-dsp: " Hari Nagalla
2021-11-30 20:52 ` Rob Herring [this message]
2021-11-22 12:27 ` [PATCH 3/4] remoteproc: k3-dsp: Extend support for C71x DSPs on " Hari Nagalla
2021-11-22 12:27 ` [PATCH 4/4] remoteproc: k3-r5: Extend support for R5F clusters " Hari Nagalla
2021-11-29 17:17 ` [PATCH 0/4] TI K3 R5F and C71x support on J721S2 Mathieu Poirier
2021-12-01 16:55 ` 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=YaaPJrqtU7Ifoe8M@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=a-govindraju@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--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: 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).