Issue with Micron QSPI flash in 4.14-rc1

[Andras Szemzo]

Hi,

> 
> This driver was developed and tested for the QSPI controller of SAMA5D2
> and I think the controller (IP version) is not quite the same on SAMV7.
> 
> I would be surprised that SPI 1-4-4 doesn't work with the Atmel QSPI
> controller of SAMV7 but let's verify it.
> 

One more addition, I quickly ported the new ASF driver to my bootloader, which also use
SFDP and shares some logic. Seems it works with SPI 1-4-4 mode on SAMV7 too:

xboot v1.0
QSPI boot selected
SPI 4-4-4 opcode=66h 
SPI 4-4-4 opcode=99h 
SPI 1-1-1 opcode=66h 
qspi_exec timeout reached
SPI 1-1-1 opcode=9Fh RX (6 bytes): 0x20 0xBA 0x20 0x10 ... 
SF: Got Manufacturer and Device ID: 20ba20
SPI 1-1-1 opcode=5Ah address=0x00000000 (3-bytes) dummy=8 RX (16 bytes): 0x53 0x46 0x44 0x50 ... 
SPI 1-1-1 opcode=5Ah address=0x00000030 (3-bytes) dummy=8 RX (36 bytes): 0xE5 0x20 0xFB 0xFF ... 
SF: WARNING: can't read above 16MiB
SPI 1-4-4 opcode=EBh address=0x00400000 (3-bytes) mode=1 (FFh) dummy=9 RX (40 bytes): 0xD0 0x0D 0xFE 0xED ... 
QSPI: dt blob: Read from 0x400000 to 0x71000000 size: 24572 bytes
SPI 1-4-4 opcode=EBh address=0x00400000 (3-bytes) mode=1 (FFh) dummy=9 RX (24572 bytes): 0xD0 0x0D 0xFE 0xED ... 
SPI 1-4-4 opcode=EBh address=0x00000000 (3-bytes) mode=1 (FFh) dummy=9 RX (64 bytes): 0x27 0x05 0x19 0x56 ... 
QSPI: Image: Read from 0x00 to 0x70007FC0, size: 3252864 bytes
SPI 1-4-4 opcode=EBh address=0x00000000 (3-bytes) mode=1 (FFh) dummy=9 RX (3252864 bytes): 0x27 0x05 0x19 0x56 ... 
starting kernel 0x70008001

Booting Linux on physical CPU 0x0
Linux version 4.14.0-rc1 (root at devel) (gcc version 4.9.2 ( 4.9.2-10)) #49 Tue Sep 26 15:24:42 CEST 2017
CPU: ARMv7-M [410fc271] revision 1 (ARMv7M), cr=00000000
CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
...