From: Rob Herring <robh@kernel.org>
To: Suman Anna <s-anna@ti.com>
Cc: devicetree@vger.kernel.org,
Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Lokesh Vutla <lokeshvutla@ti.com>,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 4/6] dt-bindings: remoteproc: Add bindings for C66x DSPs on TI K3 SoCs
Date: Mon, 13 Jul 2020 12:30:29 -0600 [thread overview]
Message-ID: <20200713183029.GA502585@bogus> (raw)
In-Reply-To: <20200612224914.7634-5-s-anna@ti.com>
On Fri, 12 Jun 2020 17:49:12 -0500, Suman Anna wrote:
> Some Texas Instruments K3 family of SoCs have one of more Digital Signal
> Processor (DSP) subsystems that are comprised of either a TMS320C66x
> CorePac and/or a next-generation TMS320C71x CorePac processor subsystem.
> Add the device tree bindings document for the C66x DSP devices on these
> SoCs. The added example illustrates the DT nodes for the first C66x DSP
> device present on the K3 J721E family of SoCs.
>
> Signed-off-by: Suman Anna <s-anna@ti.com>
> ---
> v3:
> - Refactored the common ti-sci properties "ti,sci", "ti,sci-dev-id" and
> "ti,sci-proc-ids" into a separate binding ti,k3-sci-proc.yaml.
> - Dropped the general description and maxItems against reg and reg-names
> - Added items list under reg
> - Removed the other binding references from the description for resets
> and mboxes
> - Revised the memory-region description and listed the mandatory items
> - Updated example to drop reserved-memory nodes, unused node labels
> v2: https://patchwork.kernel.org/patch/11561781/
>
> .../bindings/remoteproc/ti,k3-dsp-rproc.yaml | 139 ++++++++++++++++++
> 1 file changed, 139 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml
>
Reviewed-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:[~2020-07-13 18:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 22:49 [PATCH v3 0/6] TI K3 DSP remoteproc driver for C66x DSPs Suman Anna
2020-06-12 22:49 ` [PATCH v3 1/6] remoteproc: Introduce rproc_of_parse_firmware() helper Suman Anna
2020-06-12 22:49 ` [PATCH v3 2/6] remoteproc: k3: Add TI-SCI processor control helper functions Suman Anna
2020-06-12 22:49 ` [PATCH v3 3/6] dt-bindings: remoteproc: Add common TI SCI rproc bindings Suman Anna
2020-07-13 18:28 ` Rob Herring
2020-07-13 18:30 ` Rob Herring
2020-07-13 18:31 ` Rob Herring
2020-06-12 22:49 ` [PATCH v3 4/6] dt-bindings: remoteproc: Add bindings for C66x DSPs on TI K3 SoCs Suman Anna
2020-06-24 21:08 ` Suman Anna
2020-07-13 18:30 ` Rob Herring [this message]
2020-06-12 22:49 ` [PATCH v3 5/6] remoteproc: k3-dsp: Add a remoteproc driver of K3 C66x DSPs Suman Anna
2020-06-12 22:49 ` [PATCH v3 6/6] remoteproc: k3-dsp: Add support for L2RAM loading on " 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=20200713183029.GA502585@bogus \
--to=robh@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=grzegorz.jaszczyk@linaro.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).