linux-toradex.git/drivers/spi, branch v3.4.2

spi/spi-fsl-spi: reference correct pdata in fsl_spi_cs_control

2012-06-01T07:18:25+00:00

commit 067aa4815a9bc12a569d8a06afef50ba5773afbf upstream.

Commit 178db7d3, "spi: Fix device unregistration when unregistering
the bus master", changed spi device initialization of dev.parent pointer
to be the master's device pointer instead of his parent.

This introduced a bug in spi-fsl-spi, since its usage of spi device
pointer was not updated accordingly. This was later fixed by commit
5039a86, "spi/mpc83xx: fix NULL pdata dereference bug", but it missed
another spot on fsl_spi_cs_control function where we also need to update
usage of spi device pointer. This change address that.

Signed-off-by: Herton Ronaldo Krzesinski 
Acked-by: Joakim Tjernlund 
Signed-off-by: Grant Likely 
Signed-off-by: Greg Kroah-Hartman

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

2012-04-27T18:20:39+00:00

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:01+00:00

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:25+00:00

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:39+00:00

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:21+00:00

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:45+00:00

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:40+00:00

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:15+00:00

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:46+00:00

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