From d0478299b1d714a7001f19fb2cafeb257698a2c0 Mon Sep 17 00:00:00 2001 From: Carl-Daniel Hailfinger Date: Fri, 10 Jul 2009 21:08:55 +0000 Subject: Add SPI multicommand infrastructure Some SPI opcodes need to be sent in direct succession after each other without any chip deselect happening in between. A prominent example is WREN (Write Enable) directly before PP (Page Program). Intel calls the first opcode in such a row "preopcode". Right now, we ignore the direct succession requirement completely and it works pretty well because most onboard SPI masters have a timing or heuristics which make the problem disappear. The FT2232 SPI flasher is different. Since it is an external flasher, timing is very different to what we can expect from onboard flashers and this leads to failure at slow speeds. This patch allows any function to submit multiple SPI commands in a stream to any flasher. Support in the individual flashers isn't implemented yet, so there is one generic function which passes the each command in the stream one-by-one to the command functions of the selected SPI flash driver. Tested-by: Jakob Bornecrantz Corresponding to flashrom svn r645. Signed-off-by: Carl-Daniel Hailfinger Acked-by: Jakob Bornecrantz --- dummyflasher.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'dummyflasher.c') diff --git a/dummyflasher.c b/dummyflasher.c index 64b083e..1b51032 100644 --- a/dummyflasher.c +++ b/dummyflasher.c @@ -141,7 +141,7 @@ void dummy_chip_readn(uint8_t *buf, const chipaddr addr, size_t len) return; } -int dummy_spi_command(unsigned int writecnt, unsigned int readcnt, +int dummy_spi_send_command(unsigned int writecnt, unsigned int readcnt, const unsigned char *writearr, unsigned char *readarr) { int i; -- cgit v1.1