Hi, Brian Sorry for response this too later. Please see my comment below: > Hi Bean, > > On Tue, Dec 08, 2015 at 06:21:00AM +0000, Bean Huo 霍斌斌 wrote: > > > -----Original Message----- > > > From: Brian Norris [mailto:computersforpeace@xxxxxxxxx] > > > > > > I'll admit I'm a little fuzzy on the differences between dual and > > > quad modes on various flash manufacturers. Can you help clear it up for > me? > > > > For Micron SPI NOR spi quad mode, means that Qaud I/O prototocol, it > > follows I/O Bus width is command-address-Data 4-4-4, at this time, > > DQ0,DQ1,DQ2,DQ3 are all used to transfer address/command/data. For > > this maybe not the same between different flash manufactures. For > > example, for Spansion Qspi NOR, its all instructions are transferred > > from host to memory as a single bit serial sequence on the DQ0 signal, even > under Quad mode. Dual mode the same as Qaud mode scenario. > > > > for SPI NOR 1-1-4, means command and address are transferred on the > > DQ0, but for data, being transferred on DQ0,DQ1,DQ2,DQ3.For this, it > > is the same between different flash manufacturers. Of course, at this > > moment, SPI NOR should work under extended I/O mode. > > OK, so to make these statements *much* shorter: > > * Micron "Quad Mode" means putting the flash in a 4/4/4 mode Yes. > * Spansion (and all others?) are using 1/1/4 modes Per my experience, Spansion are using 1/4/4 in quad mode, But Macronix is the same with Micron, also putting flash into 4/4/4 mode. > > Correct? > > > > I think some of the comments on patch 2 help too, but I'll just > > > comment here for now. > > > It looks like the current driver has problems regarding the non > > > 1-x-y modes (e.g., 4-4-4), right? But I see that spi-nor.c never > > > tries to send a 4_4_4 command; it only sets read_opcode to > > > SPINOR_OP_READ_1_1_{1,2,4}. So is this an oversight in patches like > Bean's patch? > > > > For SPINOR_OP_READ_1_1_{1,2,4} commands, Spi NOR actually works > under > > Extended I/O mode, not Quad mode. They just push Spi NOR output data > > by Quad mode, Command and address still following extended I/O mode. > > The naming is confusing enough here... so in your words, "extended" > means 1/1/{1,2,4} (i.e., command, and maybe address, use 1 line, but data > goes on 4)? And "quad" means 4/4/4? Extended mode : means it is the standard spi interface, command and Address use 1 line, and how many lines being used by data, it depends on Specified command, for example, fast read command, uses 4 lines. > > For 4-4-4 I/O protocol, SPI NOR should change to Quad mode(just as my > > patch), of course, SPI controller should support this. for Micron Qspi > > NOR, under quad mode, all commands/address/data are transferred on > > DQ0,DQ1,DQ2,DQ3 signals. No matter what kind of command. > > OK, so I think your patch is broken: > > > > commit 548cd3ab54da ("mtd: spi-nor: Add quad I/O support for > Micron > > > SPI NOR") > > How did you test this? Specifically, this can't possibly have worked with a > regular drivers/spi/ controllers, since: > > (a) you're enabling 4/4/4 (i.e., "Quad mode") on the flash but > (b) m25p80_read() only sets .rx_bits for the data; i.e., it's using > 1/1/4 (i.e., "Extended mode") > I'm tempted to essentially revert that, as it looks essentially untested. It > would be nice to have a cleaner baseline before trying to extend it with > Cyrille's work. Definitely ,for my patch , it is tested and verified OK. But I add a hoot function in m25p80.c To put spi controller into quad mode as long as spi nor switch into quad mode. For this hook function patch is an independent patch with my patch, I did not submit. Because if we don't use m25p80.c driver, use new spi structure(such as : driver/mtd/spi-nor/fsl_quadspi.c) spi controller driver, This hook function patch is not necessary. > Cyrille, what do you think? Is my analysis at all correct here? (Sorry if this is > addressed elsewhere; there's a lot of text in this conversation, but I'm getting > hung up very early.) And if so, does it hurt to just drop Micron "Quad mode" > (4/4/4)? > (AIUI, this won't exactly be a panacea, since you mention bootloaders that > start us off in quad mode, so we can't use single I/O 0x9f READ > ID.) > > > > Why would we even need to enable quad modes like that, if we're not > > > going to send the 4-4-4 opcodes? > > I think, in order to high speed SPI NOR, after enable quad mode, > > SPINOR_OP_READ_1_1_{1,2,4} commands don't need any more, normal > read > > command (0x03) Can implement as them. > > OK. That's odd, but I guess it doesn't matter much. It just makes it a little less > obvious what's going on. > > > > My next question (if my understanding is roughly correct) is, do we > > > need the > > > 4-4-4 modes, and what risks come with them? I understand we can > > > shorten the command and address phases, but does that alone yield > > > much performance benefit? And I think the risk is that a given > > > system might not be prepared for the flash to be in a 4-4-4 mode, if > > > the boot code tries to use 1-x-y commands. > > > > As far as my current experience and knowledge, this still need to be > > enabled, especially for fast boot, and some IOT devices to store info into > SPI NOR. > > Do you have any data to about the speed? And you haven't addressed the > risks. There are definitely risks. Cyrille looks like he's trying to address the > risks (e.g., use volatile modes whenever possible), but it doesn't seem that > you are. > > For this patches, my current concern is that host side how to get > > different I/O protocol changes, and distinguish between different flash > manufacturers I/O mode. > > Brian ��.n��������+%������w��{.n����z�{��ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
