From: Rob Herring <robh@kernel.org>
To: Suman Anna <s-anna@ti.com>
Cc: Tony Lindgren <tony@atomide.com>, Roger Quadros <rogerq@ti.com>,
Tero Kristo <t-kristo@ti.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Suman Anna <s-anna@ti.com>
Subject: Re: [PATCH v2 1/5] dt-bindings: bus: ti-sysc: Add support for PRUSS SYSC type
Date: Tue, 3 Mar 2020 16:40:14 -0600 [thread overview]
Message-ID: <20200303224014.GA22749@bogus> (raw)
In-Reply-To: <20200227222837.7329-2-s-anna@ti.com>
On Thu, 27 Feb 2020 16:28:33 -0600, Suman Anna wrote:
> From: Roger Quadros <rogerq@ti.com>
>
> The PRUSS module has a SYSCFG which is unique. The SYSCFG
> has two additional unique fields called STANDBY_INIT and
> SUB_MWAIT in addition to regular IDLE_MODE and STANDBY_MODE
> fields. Add the bindings for this new sysc type.
>
> Cc: Rob Herring <robh+dt@kernel.org>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
> Signed-off-by: Suman Anna <s-anna@ti.com>
> ---
> v2: No changes
>
> Documentation/devicetree/bindings/bus/ti-sysc.txt | 1 +
> include/dt-bindings/bus/ti-sysc.h | 4 ++++
> 2 files changed, 5 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-03-03 22:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 22:28 [PATCH v2 0/5] ti-sysc support for PRUSS Suman Anna
2020-02-27 22:28 ` [PATCH v2 1/5] dt-bindings: bus: ti-sysc: Add support for PRUSS SYSC type Suman Anna
2020-03-03 22:40 ` Rob Herring [this message]
2020-02-27 22:28 ` [PATCH v2 2/5] " Suman Anna
2020-02-27 22:28 ` [PATCH v2 3/5] ARM: dts: AM33xx-l4: Update PRUSS interconnect target-module node Suman Anna
2020-02-28 8:33 ` Roger Quadros
2020-02-27 22:28 ` [PATCH v2 4/5] ARM: dts: AM4372: Add the PRU-ICSS " Suman Anna
2020-02-28 8:33 ` Roger Quadros
2020-02-27 22:28 ` [PATCH v2 5/5] ARM: dts: dra7: Add PRU-ICSS interconnect target-module nodes Suman Anna
2020-03-04 16:28 ` [PATCH v2 0/5] ti-sysc support for PRUSS Tony Lindgren
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=20200303224014.GA22749@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@ti.com \
--cc=s-anna@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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).