From: Rob Herring <robh@kernel.org>
To: Suman Anna <s-anna@ti.com>
Cc: linux-remoteproc@vger.kernel.org,
Tony Lindgren <tony@atomide.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-omap@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: hwlock: omap: Convert binding to YAML
Date: Wed, 9 Sep 2020 14:42:33 -0600 [thread overview]
Message-ID: <20200909204233.GA3043505@bogus> (raw)
In-Reply-To: <20200828041447.5900-1-s-anna@ti.com>
On Thu, 27 Aug 2020 23:14:47 -0500, Suman Anna wrote:
> Convert the current OMAP hwspinlock binding from text format to YAML
> format/DT schema, and delete the legacy text binding file.
>
> The new YAML binding conversion is a slightly updated version compared
> to the original. The legacy "ti,hwmods" property is now obsolete and
> is dropped altogether, and the K3 example is updated to showcase the
> actual dts node usage.
>
> Signed-off-by: Suman Anna <s-anna@ti.com>
> ---
> Hi Tony,
>
> Only warning with dtbs_check is on dm816x. What's the plan for
> converting that platform to ti,sysc?
>
> regards
> Suman
>
> .../bindings/hwlock/omap-hwspinlock.txt | 41 ----------
> .../bindings/hwlock/ti,omap-hwspinlock.yaml | 76 +++++++++++++++++++
> 2 files changed, 76 insertions(+), 41 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/hwlock/omap-hwspinlock.txt
> create mode 100644 Documentation/devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml
>
Applied, thanks!
prev parent reply other threads:[~2020-09-09 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 4:14 [PATCH] dt-bindings: hwlock: omap: Convert binding to YAML Suman Anna
2020-09-09 20:42 ` Rob Herring [this message]
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=20200909204233.GA3043505@bogus \
--to=robh@kernel.org \
--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 \
--cc=s-anna@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).