linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Schrempf Frieder <frieder.schrempf@kontron.de>
To: Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>
Cc: "boris.brezillon@bootlin.com" <boris.brezillon@bootlin.com>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>
Subject: Re: [PATCH 0/5] Prepare devicetrees for the new FSL QSPI driver
Date: Thu, 13 Dec 2018 09:45:04 +0000	[thread overview]
Message-ID: <1ad93cdf-7ba1-ff49-f330-6bbd0f6c6972@kontron.de> (raw)
In-Reply-To: <ce1442f3-357b-d647-958e-cc4a89282b79@kontron.de>

+ Shawn, Sascha

On 10.12.18 17:31, Schrempf Frieder wrote:
> Hi FSL/ARM maintainers,
> 
> On 10.12.18 17:26, Schrempf Frieder wrote:
>> From: Frieder Schrempf <frieder.schrempf@kontron.de>
>>
>> We have prepared a new driver for the FSL QSPI controller that works under
>> the SPI framework. The current devicetrees are broken because they use an
>> inconsistent scheme for assigning the reg properties.
>>
>> As, in contrast to the current driver, the new driver will use the reg
>> properties to select the correct chip, we need to fix them.
>>
>> We also add spi-[tx/rx]-bus-width to make sure the full buswidth will be used
>> and while at it clean up and remove some unused properties.
> 
> could you please consider these devicetree patches for v4.21?

Any chance to get this merged? Otherwise we would need to postpone the 
new driver even further.

All the changes to the devicetrees in this series are non-intrusive and 
uncritical, anyway.

Thanks,
Frieder

> 
> We have the new FSL QSPI driver under the SPI framework ([1]) ready, but
> we need some small fixes to the devicetrees that are currently broken.
> 
> As the new driver depends on these changes (mainly the change to the reg
> properties) and it is not possible to add compatibility for the old
> bindings, it would be really nice to have them in v4.21, so we can queue
> the driver for v4.22 or whatever the next release will be called.
> 
> Please also see [2] for some more explanation.
> 
> Thanks,
> Frieder
> 
> [1] https://patchwork.ozlabs.org/cover/1007641/
> [2] https://patchwork.ozlabs.org/patch/922817/#1925445
> 
>>
>> Frieder Schrempf (5):
>>     arm64: dts: Remove unused properties from FSL QSPI driver nodes
>>     ARM: dts: Remove unused properties from FSL QSPI driver nodes
>>     ARM: dts: imx6sx-sdb: Fix the reg properties for the FSL QSPI nodes
>>     arm64: dts: Add spi-[tx/rx]-bus-width for the FSL QSPI controller
>>     ARM: 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 MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
> 

  reply	other threads:[~2018-12-13  9:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 16:28 [PATCH 0/5] Prepare devicetrees for the new FSL QSPI driver Schrempf Frieder
2018-12-10 16:28 ` [PATCH 2/5] ARM: dts: Remove unused properties from FSL QSPI driver nodes Schrempf Frieder
2018-12-10 16:28 ` [PATCH 1/5] arm64: " Schrempf Frieder
2018-12-10 16:28 ` [PATCH 4/5] arm64: dts: Add spi-[tx/rx]-bus-width for the FSL QSPI controller Schrempf Frieder
2018-12-10 16:28 ` [PATCH 3/5] ARM: dts: imx6sx-sdb: Fix the reg properties for the FSL QSPI nodes Schrempf Frieder
2018-12-10 16:28 ` [PATCH 5/5] ARM: dts: Add spi-[tx/rx]-bus-width for the FSL QSPI controller Schrempf Frieder
2018-12-10 16:31 ` [PATCH 0/5] Prepare devicetrees for the new FSL QSPI driver Schrempf Frieder
2018-12-13  9:45   ` Schrempf Frieder [this message]
2018-12-14  0:42     ` Shawn Guo
2018-12-15 10:04       ` AW: " Schrempf Frieder
2018-12-16  7:51         ` Shawn Guo

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=1ad93cdf-7ba1-ff49-f330-6bbd0f6c6972@kontron.de \
    --to=frieder.schrempf@kontron.de \
    --cc=boris.brezillon@bootlin.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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).