From: Rob Herring <robh@kernel.org>
To: Suman Anna <s-anna@ti.com>
Cc: linux-kernel@vger.kernel.org, Lokesh Vutla <lokeshvutla@ti.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-remoteproc@vger.kernel.org,
Mathieu Poirier <mathieu.poirier@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/2] dt-bindings: remoteproc: k3-dsp: Update bindings for C71x DSPs
Date: Mon, 15 Jun 2020 10:15:59 -0600 [thread overview]
Message-ID: <20200615161559.GA1876521@bogus> (raw)
In-Reply-To: <20200612225357.8251-2-s-anna@ti.com>
On Fri, 12 Jun 2020 17:53:56 -0500, Suman Anna wrote:
> Some Texas Instruments K3 family of SoCs have one of more newer
> generation TMS320C71x CorePac processor subsystem in addition to
> the existing TMS320C66x CorePac processor subsystems. Update the
> device tree bindings document for the C71x DSP devices.
>
> The example is also updated to show the single C71 DSP present
> on J721E SoCs.
>
> Signed-off-by: Suman Anna <s-anna@ti.com>
> ---
> v3:
> - Dropped Rob's previous Reviewed-by tag due to decent changes in the
> patch
> - Replaced the minItems and maxItems from reg with actual items list
> - Dropped C71 reserved memory nodes from example
> v2: https://patchwork.kernel.org/patch/11563231/
>
> .../bindings/remoteproc/ti,k3-dsp-rproc.yaml | 68 +++++++++++++++----
> 1 file changed, 55 insertions(+), 13 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-06-15 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 22:53 [PATCH v3 0/2] Update K3 DSP remoteproc driver for C71x DSPs Suman Anna
2020-06-12 22:53 ` [PATCH v3 1/2] dt-bindings: remoteproc: k3-dsp: Update bindings " Suman Anna
2020-06-15 16:15 ` Rob Herring [this message]
2020-06-12 22:53 ` [PATCH v3 2/2] remoteproc: k3-dsp: Add 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=20200615161559.GA1876521@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=robh+dt@kernel.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).