From: Shawn Guo <shawnguo@kernel.org>
To: arm@kernel.org
Cc: Fabio Estevam <fabio.estevam@nxp.com>,
linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de,
Schrempf Frieder <frieder.schrempf@kontron.de>,
linux-imx@nxp.com
Subject: [GIT PULL] FSL QSPI device tree cleanup for 4.21
Date: Sun, 16 Dec 2018 16:48:56 +0800 [thread overview]
Message-ID: <20181216084854.GJ13243@dragon> (raw)
Hi,
As the series cleans up both i.MX/Freescale arm32 and arm64 device
trees, the pull request is based on a merge of tag imx-dt-4.21 and
imx-dt64-4.21 that have already been pulled into arm-soc next/dt branch.
This comes a bit late, and we appreciate it if you can pull it for 4.21,
as it paves the way for new QSPI driver under SPI framework to land in
the next release cycle. Thanks.
Shawn
The following changes since commit 744284fa15a1acc8601ddc0a349678e033100925:
Merge tag 'imx-dt64-4.21' into imx/qspi-dt (2018-12-16 16:20:47 +0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-qspi-dt-clean
for you to fetch changes up to 30648e9f864774388d261f42e79955362f4739e7:
arm64: dts: Add spi-[tx/rx]-bus-width for the FSL QSPI controller (2018-12-16 16:24:01 +0800)
----------------------------------------------------------------
Freescale QSPI device tree cleanup for 4.21:
- It contains a series from Schrempf Frieder that cleans up FSL QSPI
device tree nodes. The current device trees are broken because they
use an inconsistent scheme for assigning the reg properties. It
becomes a problem with ongoing QSPI driver under SPI framework. So
the cleanup is a preparation for new driver landing in the next
cycle.
----------------------------------------------------------------
Frieder Schrempf (5):
ARM: dts: Remove unused properties from FSL QSPI driver nodes
ARM: dts: imx6sx-sdb: Fix the reg properties for the FSL QSPI nodes
ARM: dts: Add spi-[tx/rx]-bus-width for the FSL QSPI controller
arm64: dts: Remove unused properties from FSL QSPI driver nodes
arm64: dts: Add spi-[tx/rx]-bus-width for the FSL QSPI controller
arch/arm/boot/dts/imx6sx-sdb-reva.dts | 8 ++++++--
arch/arm/boot/dts/imx6sx-sdb.dts | 8 ++++++--
arch/arm/boot/dts/imx6ul-14x14-evk.dtsi | 2 ++
arch/arm/boot/dts/ls1021a-moxa-uc-8410a.dts | 5 ++---
arch/arm64/boot/dts/freescale/fsl-ls1043a-qds.dts | 3 ++-
arch/arm64/boot/dts/freescale/fsl-ls1046a-qds.dts | 4 ++--
arch/arm64/boot/dts/freescale/fsl-ls1046a-rdb.dts | 6 ++++--
arch/arm64/boot/dts/freescale/fsl-ls208xa-qds.dtsi | 4 ++++
8 files changed, 28 insertions(+), 12 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2018-12-16 8:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 8:48 Shawn Guo [this message]
2018-12-20 15:50 ` [GIT PULL] FSL QSPI device tree cleanup for 4.21 Arnd Bergmann
2018-12-20 16:03 ` Schrempf Frieder
2018-12-20 16:11 ` Arnd Bergmann
2018-12-20 16:23 ` Schrempf Frieder
2018-12-20 16:32 ` Arnd Bergmann
2018-12-20 18:23 ` Geert Uytterhoeven
2018-12-20 22:41 ` Arnd Bergmann
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=20181216084854.GJ13243@dragon \
--to=shawnguo@kernel.org \
--cc=arm@kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=frieder.schrempf@kontron.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.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).