devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Hari Nagalla <hnagalla@ti.com>
Cc: andersson@kernel.org, devicetree@vger.kernel.org,
	p.zabel@pengutronix.de, linux-remoteproc@vger.kernel.org,
	robh+dt@kernel.org, linux-kernel@vger.kernel.org,
	krzysztof.kozlowski+dt@linaro.org, s-anna@ti.com,
	praneeth@ti.com, nm@ti.com, vigneshr@ti.com, a-bhatia1@ti.com,
	j-luthra@ti.com, devarsht@ti.com
Subject: Re: [PATCH v2 0/2] Add C7xv DSP for AM62A
Date: Fri, 13 Jan 2023 14:45:44 -0700	[thread overview]
Message-ID: <20230113214544.GA2956142@p14s> (raw)
In-Reply-To: <20221230132453.32022-1-hnagalla@ti.com>

On Fri, Dec 30, 2022 at 07:24:51AM -0600, Hari Nagalla wrote:
> AM62A SoC family has a C7xv DSP subsystem with Analytics engine. This
> susbystem is intended for deep learning purposes. C7xv is similar to C71
> DSPs on K3 J7 SoCs with additional harware accelerators and IP updates
> for deep learining.
> 
> Hari Nagalla (1):
>   dt-bindings: remoteproc: k3-dsp: update bindings for AM62A SoCs
> 
> Jai Luthra (1):
>   remoteproc: k3-c7x: Add support for C7xv DSP on AM62A SoC
> 
>  .../bindings/remoteproc/ti,k3-dsp-rproc.yaml         |  3 +++
>  drivers/remoteproc/ti_k3_dsp_remoteproc.c            | 12 ++++++++++++
>  2 files changed, 15 insertions(+)
>

Applied - thanks
Mathieu

> -- 
> 2.17.1
> 

      parent reply	other threads:[~2023-01-13 21:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30 13:24 [PATCH v2 0/2] Add C7xv DSP for AM62A Hari Nagalla
2022-12-30 13:24 ` [PATCH v2 1/2] dt-bindings: remoteproc: k3-dsp: update bindings for AM62A SoCs Hari Nagalla
2023-01-02  9:33   ` Krzysztof Kozlowski
2022-12-30 13:24 ` [PATCH v2 2/2] remoteproc: k3-c7x: Add support for C7xv DSP on AM62A SoC Hari Nagalla
2023-01-13 21:45 ` Mathieu Poirier [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=20230113214544.GA2956142@p14s \
    --to=mathieu.poirier@linaro.org \
    --cc=a-bhatia1@ti.com \
    --cc=andersson@kernel.org \
    --cc=devarsht@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hnagalla@ti.com \
    --cc=j-luthra@ti.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=p.zabel@pengutronix.de \
    --cc=praneeth@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=s-anna@ti.com \
    --cc=vigneshr@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).