devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Mark Brown <broonie@kernel.org>,
	linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH 0/3] DTC fixes for Arm pl022 bindings
Date: Mon, 28 Feb 2022 18:13:42 +0530	[thread overview]
Message-ID: <20220228124345.99474-1-singh.kuldeep87k@gmail.com> (raw)

This patchset helps in resolving dtc warnings for arm pl022 bindings.
Fixing requires updation to clock and clock-names properties.
One more dts fix is required to eliminate all warnings which will be
sent from other tree.

Please note, this patch is based on top of
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git, for-next

Kuldeep Singh (3):
  dt-bindings: spi: Update clocks property for ARM pl022
  dt-bindings: spi: Update clock-names property for ARM pl022
  dt-bindings: spi: Add spiclk to clock-names property in pl022

 .../devicetree/bindings/spi/spi-pl022.yaml          | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

-- 
2.25.1


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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28 12:43 Kuldeep Singh [this message]
2022-02-28 12:43 ` [PATCH 1/3] dt-bindings: spi: Update clocks property for ARM pl022 Kuldeep Singh
2022-02-28 14:26   ` Robin Murphy
2022-02-28 15:11     ` Mark Brown
2022-02-28 15:27       ` Robin Murphy
2022-02-28 15:46         ` Mark Brown
2022-02-28 16:01           ` Robin Murphy
2022-02-28 12:43 ` [PATCH 2/3] dt-bindings: spi: Update clock-names " Kuldeep Singh
2022-02-28 12:43 ` [PATCH 3/3] dt-bindings: spi: Add spiclk to clock-names property in pl022 Kuldeep Singh
2022-02-28 14:36   ` Robin Murphy
2022-03-02 19:05     ` Kuldeep Singh

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=20220228124345.99474-1-singh.kuldeep87k@gmail.com \
    --to=singh.kuldeep87k@gmail.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@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).