devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Nishanth Menon <nm@ti.com>,
	Santosh Shilimkar <ssantosh@kernel.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	Kishon Vijay Abraham I <kishon@ti.com>
Subject: [PATCH v2 0/3] soc: ti: Enable PRUSS-M on K3 AM62x SoCs
Date: Thu, 2 Jun 2022 17:36:10 +0530	[thread overview]
Message-ID: <20220602120613.2175-1-kishon@ti.com> (raw)

Series adds AM62x specific compatible string to enable PRUSS-M in
AM62x SoCs.

Changes from v1:
1) Added a new patch to re-arrange "compatible" in alphabetic
   order

v1: https://lore.kernel.org/r/20220427072703.4898-1-kishon@ti.com

Kishon Vijay Abraham I (3):
  dt-bindings: soc: ti: pruss: Re-arrange "compatible" in alphabetic
    order
  dt-bindings: soc: ti: pruss: Update bindings for K3 AM62x SoCs
  soc: ti: pruss: Enable support for PRUSS-M subsystem on K3 AM62x SoCs

 Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml | 5 +++--
 drivers/soc/ti/pruss.c                                 | 1 +
 2 files changed, 4 insertions(+), 2 deletions(-)

-- 
2.17.1


             reply	other threads:[~2022-06-02 12:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 12:06 Kishon Vijay Abraham I [this message]
2022-06-02 12:06 ` [PATCH v2 1/3] dt-bindings: soc: ti: pruss: Re-arrange "compatible" in alphabetic order Kishon Vijay Abraham I
2022-06-02 12:20   ` Krzysztof Kozlowski
2022-06-02 12:06 ` [PATCH v2 2/3] dt-bindings: soc: ti: pruss: Update bindings for K3 AM62x SoCs Kishon Vijay Abraham I
2022-06-02 12:20   ` Krzysztof Kozlowski
2022-06-02 12:06 ` [PATCH v2 3/3] soc: ti: pruss: Enable support for PRUSS-M subsystem on " Kishon Vijay Abraham I
2022-07-07  1:32 ` [PATCH v2 0/3] soc: ti: Enable PRUSS-M " Nishanth Menon

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=20220602120613.2175-1-kishon@ti.com \
    --to=kishon@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=ssantosh@kernel.org \
    /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).