linux-stable.git/include/linux/spi/spi.h, branch linux-3.12.y

Merge remote-tracking branch 'spi/topic/qspi' into spi-next

2013-09-01T12:49:06+00:00

Merge remote-tracking branch 'spi/topic/msglen' into spi-next

2013-09-01T12:48:58+00:00

Merge remote-tracking branch 'spi/topic/checks' into spi-next

2013-09-01T12:48:48+00:00

Merge remote-tracking branch 'spi/topic/quad' into spi-qspi

2013-08-23T11:00:15+00:00

spi: DUAL and QUAD support

2013-08-22T12:47:29+00:00

fix the previous patch some mistake below:
1. DT in slave node, use "spi-tx-nbits = <1/2/4>" in place of using
   "spi-tx-dual, spi-tx-quad" directly, same to rx. So correct the
   previous way to get the property in @of_register_spi_devices().
2. Change the value of transfer bit macro(SPI_NBITS_SINGLE, SPI_NBITS_DUAL
   SPI_NBITS_QUAD) to 0x01, 0x02 and 0x04 to match the actual wires.
3. Add the following check
   (1)keep the tx_nbits and rx_nbits in spi_transfer is not beyond the
      single, dual and quad.
   (2)keep tx_nbits and rx_nbits are contained by @spi_device->mode
      example: if @spi_device->mode = DUAL, then tx/rx_nbits can not be set
               to QUAD(SPI_NBITS_QUAD)
   (3)if "@spi_device->mode & SPI_3WIRE", then tx/rx_nbits should be in
      single(SPI_NBITS_SINGLE)

Signed-off-by: wangyuhang 
Signed-off-by: Mark Brown

spi: fix SPI_BIT_MASK so it always fits into 32-bits

2013-08-02T10:31:22+00:00

On a 64-bit platform, ~0UL fills 64-bits, which causes SPI_BIT_MASK(32)
not to fit into 32 bits. This causes a warning when the result is assigned
to a 32-bit variable. Use ~0U instead to prevent this. This fixes:

drivers/spi/spi-gpio.c: In function 'spi_gpio_probe':
drivers/spi/spi-gpio.c:446:2: warning: large integer implicitly truncated to unsigned type [-Woverflow]

Reported-by: kbuild test robot 
Signed-off-by: Stephen Warren 
Signed-off-by: Mark Brown

spi: Provide core support for runtime PM during transfers

2013-07-29T16:59:20+00:00

Most SPI drivers that implement runtime PM support use identical code to
do so: they acquire a runtime PM lock in prepare_transfer_hardware() and
then they release it in unprepare_transfer_hardware(). The variations in
this are mostly missing error checking and the choice to use autosuspend.

Since these runtime PM calls are normally the only thing in the prepare
and unprepare callbacks and the autosuspend API transparently does the
right thing on devices with autosuspend disabled factor all of this out
into the core with a flag to enable the behaviour.

Signed-off-by: Mark Brown 
Reviewed-by: Stephen Warren 
Acked-by: Linus Walleij

driver: spi: Modify core to compute the message length

2013-07-18T15:22:01+00:00

Make spi core calculate the message length while
populating the other transfer parameters.

Usecase, driver can use it to populate framelength filed in their
controller.

Signed-off-by: Sourav Poddar 
Signed-off-by: Mark Brown

spi: Support transfer speed checking in the core

2013-07-15T10:34:51+00:00

Allow drivers to avoid implementing their own checks for simple rates by
specifying the limits in the master structure.

Signed-off-by: Mark Brown

spi: fix incorrect handling of min param in SPI_BPW_RANGE_MASK

2013-06-01T18:46:16+00:00

SPI_BPW_RANGE_MASK is intended to work by calculating two masks; one
representing support for all bits up-to-and-including the "max" supported
value, and one representing support for all bits up-to-but-not-including
the "min" supported value, and then taking the difference between the
two, resulting in a mask representing support for all bits between
(inclusive) the min and max values.

However, the second mask ended up representing all bits up-to-and-
including rather up-to-but-not-including. Fix this bug.

Signed-off-by: Stephen Warren 
Signed-off-by: Mark Brown