linux/drivers/spi, branch v3.4

spi/spi-bfin5xx: Fix flush of last bit after each spi transfer

2012-04-27T18:20:39Z

This patch ensures that the last bit of a transfer gets correctly flushed out of the register. Signed-off-by: Scott Jiang Signed-off-by: Grant Likely

spi/spi-bfin5xx: fix reversed if condition in interrupt mode

2012-04-27T18:19:01Z

This condition is used to determine 8 bits or 16 and 32 bits transfer. Obviously it is reversed. Signed-off-by: Scott Jiang Signed-off-by: Grant Likely

spi/spi_bfin_sport: drop bits_per_word from client data

2012-04-27T18:17:25Z

Since the member was dropped from the common Blackfin header, we need to stop using it in the SPORT driver too. Signed-off-by: Mike Frysinger Signed-off-by: Scott Jiang Signed-off-by: Grant Likely

spi/bfin_spi: drop bits_per_word from client data

2012-04-27T18:16:39Z

No other SPI controller has this field, and SPI clients should be setting this up in their own drivers. So drop it from the Blackfin controller to keep people from using it. Signed-off-by: Mike Frysinger Signed-off-by: Scott Jiang Signed-off-by: Grant Likely

spi/spi-bfin-sport: move word length setup to transfer handler

2012-04-27T18:16:21Z

Each transfer may have its own bits per word. Signed-off-by: Scott Jiang Signed-off-by: Grant Likely

spi/bfin5xx: rename config macro name for bfin5xx spi controller driver

2012-04-27T18:15:45Z

This controller is only for blackfin 5xx soc, so rename it to BFIN5XX Signed-off-by: Scott Jiang Signed-off-by: Grant Likely

spi/pl022: Allow request for higher frequency than maximum possible

2012-04-27T18:07:40Z

Currently, if we request for frequency greater than maximum possible, spi driver returns error. For example, if the spi block src frequency is 333/4 MHz, i.e. 83.33.. MHz, maximum frequency programmable would be src/2. Which would come around 41.6... It is difficult to pass frequency in these figures. We normally try to program in round figures, like 42 MHz and it should get programmed to <= requested_frequency, i.e. 41.6... For this to happen, we must not return error even if requested freq is higher than max possible. But should program it to max possible. Reported-by: Vinit Kamalaksha Shenoy Signed-off-by: Viresh Kumar Acked-by: Linus Walleij Signed-off-by: Grant Likely

spi/bcm63xx: set master driver mode_bits.

2012-04-27T17:19:15Z

We were not properly advertising the MODE bits supported by this driver, fix that. Signed-off-by: Florian Fainelli Signed-off-by: Grant Likely

spi/bcm63xx: don't use the stopping state

2012-04-27T17:16:46Z

We do not need to use a flag to indicate if the master driver is stopping it is sufficient to perform spi master unregistering in the platform driver's remove function. Signed-off-by: Florian Fainelli Signed-off-by: Grant Likely

spi/bcm63xx: convert to the pump message infrastructure

2012-04-27T17:15:41Z

This patch converts the bcm63xx SPI driver to use the SPI infrastructure pump message queue. Since we were previously sleeping in the SPI driver's transfer() function (which is not allowed) this is now fixed as well. To complete that conversion a certain number of changes have been made: - the transfer len is split into multiple hardware transfers in case its size is bigger than the hardware FIFO size - the FIFO refill is no longer done in the interrupt context, which was a bad idea leading to quick interrupt handler re-entrancy Tested-by: Tanguy Bouzeloc Signed-off-by: Florian Fainelli Signed-off-by: Grant Likely