Message ID | 20190107092823.11188-6-frieder.schrempf@kontron.de (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | None | expand |
On Mon, Jan 07, 2019 at 09:29:54AM +0000, Schrempf Frieder wrote: > From: Frieder Schrempf <frieder.schrempf@kontron.de> > > After switching to the new FSL QSPI driver the property > 'fsl,qspi-has-second-chip' is not needed anymore. > > The driver now uses the 'reg' property to determine the bus and > the chipselect. > > Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de> Applied, thanks.
Hi Shawn, On 13.01.19 04:31, Shawn Guo wrote: > On Mon, Jan 07, 2019 at 09:29:54AM +0000, Schrempf Frieder wrote: >> From: Frieder Schrempf <frieder.schrempf@kontron.de> >> >> After switching to the new FSL QSPI driver the property >> 'fsl,qspi-has-second-chip' is not needed anymore. >> >> The driver now uses the 'reg' property to determine the bus and >> the chipselect. >> >> Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de> > > Applied, thanks. I just noticed, that this and the arm64 patch depend on the driver changes for 5.1 that go through the SPI tree. So I guess we can't be sure that this will be merged in the right order and we need to delay this cleanup to 5.2, or am I wrong? Thanks, Frieder
On Mon, Jan 14, 2019 at 08:18:49AM +0000, Schrempf Frieder wrote: > Hi Shawn, > > On 13.01.19 04:31, Shawn Guo wrote: > > On Mon, Jan 07, 2019 at 09:29:54AM +0000, Schrempf Frieder wrote: > >> From: Frieder Schrempf <frieder.schrempf@kontron.de> > >> > >> After switching to the new FSL QSPI driver the property > >> 'fsl,qspi-has-second-chip' is not needed anymore. > >> > >> The driver now uses the 'reg' property to determine the bus and > >> the chipselect. > >> > >> Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de> > > > > Applied, thanks. > > I just noticed, that this and the arm64 patch depend on the driver > changes for 5.1 that go through the SPI tree. So I guess we can't be > sure that this will be merged in the right order and we need to delay > this cleanup to 5.2, or am I wrong? You are right. I just dropped the both patches. Ping me or resend when they are ready to go. Shawn
On 15.01.19 16:18, Shawn Guo wrote: > On Mon, Jan 14, 2019 at 08:18:49AM +0000, Schrempf Frieder wrote: >> Hi Shawn, >> >> On 13.01.19 04:31, Shawn Guo wrote: >>> On Mon, Jan 07, 2019 at 09:29:54AM +0000, Schrempf Frieder wrote: >>>> From: Frieder Schrempf <frieder.schrempf@kontron.de> >>>> >>>> After switching to the new FSL QSPI driver the property >>>> 'fsl,qspi-has-second-chip' is not needed anymore. >>>> >>>> The driver now uses the 'reg' property to determine the bus and >>>> the chipselect. >>>> >>>> Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de> >>> >>> Applied, thanks. >> >> I just noticed, that this and the arm64 patch depend on the driver >> changes for 5.1 that go through the SPI tree. So I guess we can't be >> sure that this will be merged in the right order and we need to delay >> this cleanup to 5.2, or am I wrong? > > You are right. I just dropped the both patches. Ping me or resend when > they are ready to go. Thanks, will do so. Frieder
diff --git a/arch/arm/boot/dts/ls1021a-moxa-uc-8410a.dts b/arch/arm/boot/dts/ls1021a-moxa-uc-8410a.dts index 6a83f30029ea..d3a1a73ae97e 100644 --- a/arch/arm/boot/dts/ls1021a-moxa-uc-8410a.dts +++ b/arch/arm/boot/dts/ls1021a-moxa-uc-8410a.dts @@ -203,7 +203,6 @@ }; &qspi { - fsl,qspi-has-second-chip; status = "okay"; flash: flash@0 {