All of lore.kernel.org
 help / color / mirror / Atom feed
From: Schrempf Frieder <frieder.schrempf@kontron.de>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v6 1/9] ARM: dts: Reflect change of FSL QSPI driver and remove unused properties
Date: Tue, 27 Nov 2018 11:16:55 +0000	[thread overview]
Message-ID: <dddc8370-1059-4565-5556-4baf91f7e432@kontron.de> (raw)
In-Reply-To: <20181127110134.7xdwo7ird44qj2ih@pengutronix.de>

Hi Uwe,

On 27.11.18 12:01, Uwe Kleine-König wrote:
> Hello,
> 
> On Tue, Nov 27, 2018 at 10:24:19AM +0000, Schrempf Frieder wrote:
>> The FSL QSPI driver will be moved to the SPI framework and it then
>> acts as a SPI controller. Therefore the subnodes need to set
>> spi-[rx/tx]-bus-width = <4>, so quad mode is used just as before.
>>
>> Also the properties 'bus-num', 'fsl,spi-num-chipselects' and
>> 'fsl,spi-flash-chipselects' were never read by the driver and
>> can be removed.
>>
>> The 'reg' properties are adjusted to reflect what bus and
>> chipselect the flash is connected to, as the new driver needs
>> this information.
>>
>> The property 'fsl,qspi-has-second-chip' is not needed anymore
>> and will be removed after the old driver was disabled to avoid
>> breaking ls1021a-moxa-uc-8410a.dts.
>>
>> Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de>
> 
> do we need to change the binding document accordingly?

Bindings are changed here: https://patchwork.ozlabs.org/patch/1003761/

Thanks,
Frieder

  reply	other threads:[~2018-11-27 11:17 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 10:23 [PATCH v6 0/9] Port the FSL QSPI driver to the SPI framework Schrempf Frieder
2018-11-27 10:24 ` [PATCH v6 1/9] ARM: dts: Reflect change of FSL QSPI driver and remove unused properties Schrempf Frieder
2018-11-27 10:24   ` Schrempf Frieder
2018-11-27 10:24   ` Schrempf Frieder
2018-11-27 11:01   ` Uwe Kleine-König
2018-11-27 11:01     ` Uwe Kleine-König
2018-11-27 11:01     ` Uwe Kleine-König
2018-11-27 11:01     ` Uwe Kleine-König
2018-11-27 11:16     ` Schrempf Frieder [this message]
2018-11-27 14:51     ` Schrempf Frieder
2018-11-27 14:51       ` Schrempf Frieder
2018-11-27 14:51       ` Schrempf Frieder
2018-11-27 14:51       ` Schrempf Frieder
2018-11-27 14:51       ` Schrempf Frieder
2018-11-27 10:24 ` [PATCH v6 2/9] arm64: " Schrempf Frieder
2018-11-27 10:24   ` Schrempf Frieder
2018-11-27 10:24   ` Schrempf Frieder
2018-11-27 10:24   ` Schrempf Frieder
2018-11-27 10:24 ` [PATCH v6 3/9] spi: Add a driver for the Freescale/NXP QuadSPI controller Schrempf Frieder
2018-11-28  8:28   ` Schrempf Frieder
2018-11-29 11:38     ` Yogesh Narayan Gaur
2018-11-29 11:53       ` Schrempf Frieder
2018-11-29 16:30         ` Han Xu
2018-11-29 17:35           ` Schrempf Frieder
2018-12-03 20:54             ` Han Xu
2018-12-04  8:20               ` Schrempf Frieder
2018-11-30  4:33         ` Yogesh Narayan Gaur
2018-11-27 10:24 ` [PATCH v6 4/9] dt-bindings: spi: Move the bindings for the FSL QSPI driver Schrempf Frieder
2018-11-27 10:24 ` [PATCH v6 5/9] dt-bindings: spi: Adjust " Schrempf Frieder
2018-11-27 10:24   ` Schrempf Frieder
2018-11-27 10:24   ` Schrempf Frieder
2018-11-27 10:24 ` [PATCH v6 6/9] mtd: fsl-quadspi: Remove the driver as it was replaced by spi-fsl-qspi.c Schrempf Frieder
2018-11-27 10:24 ` [PATCH v6 7/9] ARM: dts: ls1021a: Remove fsl,qspi-has-second-chip as it is not used Schrempf Frieder
2018-11-27 10:24   ` [PATCH v6 7/9] ARM: dts: ls1021a: Remove fsl, qspi-has-second-chip " Schrempf Frieder
2018-11-27 10:24   ` Schrempf Frieder
2018-11-27 10:24   ` [PATCH v6 7/9] ARM: dts: ls1021a: Remove fsl,qspi-has-second-chip " Schrempf Frieder
2018-11-27 10:24   ` Schrempf Frieder
2018-11-27 10:24 ` [PATCH v6 8/9] ARM64: dts: ls1046a: " Schrempf Frieder
2018-11-27 10:24   ` Schrempf Frieder
2018-11-27 10:24   ` Schrempf Frieder
2018-11-27 10:24   ` Schrempf Frieder
2018-11-27 10:24 ` [PATCH v6 9/9] MAINTAINERS: Move the Freescale QSPI driver to the SPI framework Schrempf Frieder
2018-11-27 10:24   ` Schrempf Frieder

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=dddc8370-1059-4565-5556-4baf91f7e432@kontron.de \
    --to=frieder.schrempf@kontron.de \
    --cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.