From: Rob Herring <robh@kernel.org>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
Nishanth Menon <nm@ti.com>, Dave Gerlach <d-gerlach@ti.com>,
linux-arm-kernel@lists.infradead.org,
Sekhar Nori <nsekhar@ti.com>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Lokesh Vutla <lokeshvutla@ti.com>, Tero Kristo <t-kristo@ti.com>
Subject: Re: [PATCH v4 1/2] dt-bindings: soc: ti: add binding for k3 platforms chipid module
Date: Tue, 19 May 2020 12:54:27 -0600 [thread overview]
Message-ID: <20200519185427.GA468784@bogus> (raw)
In-Reply-To: <20200512123449.16517-2-grygorii.strashko@ti.com>
On Tue, 12 May 2020 15:34:48 +0300, Grygorii Strashko wrote:
> Add DT binding for Texas Instruments K3 Multicore SoC platforms chipid
> module which is represented by CTRLMMR_xxx_JTAGID register and contains
> information about SoC id and revision.
>
> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
> Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>
> Reviewed-by: Tero Kristo <t-kristo@ti.com>
> ---
> .../bindings/soc/ti/k3-socinfo.yaml | 40 +++++++++++++++++++
> 1 file changed, 40 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/soc/ti/k3-socinfo.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-05-19 18:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 12:34 [PATCH v4 0/2] soc: ti: add k3 platforms chipid module driver Grygorii Strashko
2020-05-12 12:34 ` [PATCH v4 1/2] dt-bindings: soc: ti: add binding for k3 platforms chipid module Grygorii Strashko
2020-05-19 18:54 ` Rob Herring [this message]
2020-05-12 12:34 ` [PATCH v4 2/2] soc: ti: add k3 platforms chipid module driver Grygorii Strashko
2020-05-29 18:22 ` [PATCH v4 0/2] " Grygorii Strashko
2020-05-29 18:34 ` Arnd Bergmann
2020-05-29 19:19 ` santosh.shilimkar
2020-05-29 19:39 ` Grygorii Strashko
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=20200519185427.GA468784@bogus \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=t-kristo@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).