From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
soc@kernel.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Subject: [PATCH v2 0/3] PL022 DT fixes for seattle, lg and lpc platform
Date: Fri, 11 Mar 2022 15:07:57 +0530 [thread overview]
Message-ID: <20220311093800.18778-1-singh.kuldeep87k@gmail.com> (raw)
This patchset is an attempt to fix DTs which are not compliant with
pl022 spi binding. Please note, there are other fixes required also
which are sent from other trees.
As git trees for these platforms are not available, Rob advised me to
seek help from soc tree maintainers.
Arnd and Olof, could you please help in reviewing and merging this
patchset.
These patches are base on
git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git, arm/dt
Link to v1 below:
https://lore.kernel.org/linux-devicetree/20220311025932.GD54098@9a2d8922b8f1/T/#m734e470b3be87b7591b3e6d618e4c777f8e61981
Patch1: Fix spi clock for amd seattle platform
Patch2: Fix spi clock for lg platforms
Patch3: Fix spi clock for lpc platform
Kuldeep Singh (3):
arm64: dts: seattle: Update spi clock properties
arm64: dts: lg131x: Update spi clock properties
ARM: dts: lpc32xx: Update spi clock properties
arch/arm/boot/dts/lpc32xx.dtsi | 8 ++++----
arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi | 8 ++++----
arch/arm64/boot/dts/lg/lg1312.dtsi | 8 ++++----
arch/arm64/boot/dts/lg/lg1313.dtsi | 8 ++++----
4 files changed, 16 insertions(+), 16 deletions(-)
--
2.25.1
next reply other threads:[~2022-03-11 9:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 9:37 Kuldeep Singh [this message]
2022-03-11 9:37 ` [PATCH v2 1/3] arm64: dts: seattle: Update spi clock properties Kuldeep Singh
2022-03-11 9:37 ` [PATCH v2 2/3] arm64: dts: lg131x: " Kuldeep Singh
2022-03-11 9:38 ` [PATCH v2 3/3] ARM: dts: lpc32xx: " Kuldeep Singh
2022-03-11 13:20 ` Vladimir Zapolskiy
2022-03-11 13:38 ` Arnd Bergmann
2022-03-11 14:07 ` Vladimir Zapolskiy
2022-03-11 14:33 ` Krzysztof Kozlowski
2022-03-11 21:26 ` Vladimir Zapolskiy
2022-03-12 10:23 ` Krzysztof Kozlowski
2022-03-12 12:26 ` Vladimir Zapolskiy
2022-03-14 11:43 ` Robin Murphy
2022-03-14 11:50 ` Vladimir Zapolskiy
2022-03-14 12:20 ` Robin Murphy
2022-03-14 12:32 ` Arnd Bergmann
2022-03-14 17:55 ` Robin Murphy
2022-03-14 12:34 ` Vladimir Zapolskiy
[not found] ` <CAHUNapQMaBZ2-yJR10Qv+Pix9BA3AGSgjBaMBB9zJTTLLOGSkg@mail.gmail.com>
2022-03-27 16:27 ` Vladimir Zapolskiy
2022-03-27 18:32 ` Trevor Woerner
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=20220311093800.18778-1-singh.kuldeep87k@gmail.com \
--to=singh.kuldeep87k@gmail.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@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
all inboxes | Powered by JetHome®