From: Suman Anna <s-anna@ti.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
linux-remoteproc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] Add HwSpinlock support for TI K3 SoCs
Date: Mon, 24 Jun 2019 15:38:52 -0500 [thread overview]
Message-ID: <90211f72-7ce4-94e5-aef7-bbe14266dfbb@ti.com> (raw)
In-Reply-To: <20190531021321.14025-1-s-anna@ti.com>
Hi Bjorn,
On 5/30/19 9:13 PM, Suman Anna wrote:
> Hi Bjorn,
>
> The following series adds the support for the HwSpinlock IP present
> on the newer TI K3 AM65x and J721E SoCs. The first 2 patches are
> related to the K3 support, and the last patch is a minor debug related
> trace to see the number of locks registered on each SoC.
>
> I will be posting the DT nodes once the binding is acked.
If you do not have any comments, can you please pick up this series for
5.3 merge window?
Thanks,
Suman
>
> regards
> Suman
>
> Suman Anna (3):
> dt-bindings: hwlock: Update OMAP binding for TI K3 SoCs
> hwspinlock/omap: Add support for TI K3 SoCs
> hwspinlock/omap: Add a trace during probe
>
> .../bindings/hwlock/omap-hwspinlock.txt | 25 +++++++++++++++----
> drivers/hwspinlock/Kconfig | 2 +-
> drivers/hwspinlock/omap_hwspinlock.c | 4 +++
> 3 files changed, 25 insertions(+), 6 deletions(-)
>
next prev parent reply other threads:[~2019-06-24 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 2:13 [PATCH 0/3] Add HwSpinlock support for TI K3 SoCs Suman Anna
2019-05-31 2:13 ` [PATCH 1/3] dt-bindings: hwlock: Update OMAP binding " Suman Anna
2019-05-31 2:13 ` [PATCH 2/3] hwspinlock/omap: Add support " Suman Anna
2019-05-31 2:13 ` [PATCH 3/3] hwspinlock/omap: Add a trace during probe Suman Anna
2019-06-24 20:38 ` Suman Anna [this message]
2019-06-29 18:57 ` [PATCH 0/3] Add HwSpinlock support for TI K3 SoCs Bjorn Andersson
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=90211f72-7ce4-94e5-aef7-bbe14266dfbb@ti.com \
--to=s-anna@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=robh+dt@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).