linux-remoteproc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Suman Anna <s-anna@ti.com>
Cc: devicetree@vger.kernel.org,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Lokesh Vutla <lokeshvutla@ti.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-remoteproc@vger.kernel.org, Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH v5 1/6] dt-bindings: arm: keystone: Add common TI SCI bindings
Date: Thu, 23 Jul 2020 11:02:34 -0600	[thread overview]
Message-ID: <20200723170234.GA535571@bogus> (raw)
In-Reply-To: <20200721223617.20312-2-s-anna@ti.com>

On Tue, 21 Jul 2020 17:36:12 -0500, Suman Anna wrote:
> Add a bindings document that defines the common TI SCI properties
> used by various K3 device management nodes such as clock controllers,
> interrupt controllers, reset controllers or remoteproc devices.
> 
> The required properties for each device management node shall be
> specified in the respective binding document.
> 
> Signed-off-by: Suman Anna <s-anna@ti.com>
> ---
> v5:
>  - New patch refactored out for usage by remoteproc and other TI SCI
>    interrupt controller bindings
>  - Patch based on remoteproc ti,k3-sci-proc.yaml binding (v4 patch 3)
>    with revised overall description and ti,sci-dev-id and no required
>    properties
> v4: https://patchwork.kernel.org/patch/11671455/
>  - Addressed both of Rob's review comments on ti,sci-proc-ids property
> v3: https://patchwork.kernel.org/patch/11602317/
> 
>  .../arm/keystone/ti,k3-sci-common.yaml        | 44 +++++++++++++++++++
>  MAINTAINERS                                   |  1 +
>  2 files changed, 45 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/arm/keystone/ti,k3-sci-common.yaml
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2020-07-23 17:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 22:36 [PATCH v5 0/6] TI K3 DSP remoteproc driver for C66x DSPs Suman Anna
2020-07-21 22:36 ` [PATCH v5 1/6] dt-bindings: arm: keystone: Add common TI SCI bindings Suman Anna
2020-07-23 17:02   ` Rob Herring [this message]
2020-07-21 22:36 ` [PATCH v5 2/6] remoteproc: Introduce rproc_of_parse_firmware() helper Suman Anna
2020-07-21 22:36 ` [PATCH v5 3/6] remoteproc: k3: Add TI-SCI processor control helper functions Suman Anna
2020-07-21 22:36 ` [PATCH v5 4/6] dt-bindings: remoteproc: Add bindings for C66x DSPs on TI K3 SoCs Suman Anna
2020-07-21 22:36 ` [PATCH v5 5/6] remoteproc: k3-dsp: Add a remoteproc driver of K3 C66x DSPs Suman Anna
2020-07-21 22:36 ` [PATCH v5 6/6] remoteproc: k3-dsp: Add support for L2RAM loading on " Suman Anna
2020-07-29  0:20 ` [PATCH v5 0/6] TI K3 DSP remoteproc driver for " patchwork-bot+linux-remoteproc

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=20200723170234.GA535571@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=nm@ti.com \
    --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).