linux-toradex.git/drivers/spi, branch PD13.0.0alpha Linux kernel for Apalis and Colibri modules ENGR00181390-2: qspi: Add Quad SPI driver support for Vybrid 2012-10-17T18:37:24+00:00 Alison Wang b18965@freescale.com 2012-09-28T05:21:42+00:00 b2fcdda7a78d05ac0b75d52ffc991f1c62d87178 Add Quad SPI driver support for Vybrid. Signed-off-by: Alison Wang <b18965@freescale.com> Xiaochun Li <b41219@freescale.com> 
Add Quad SPI driver support for Vybrid.

Signed-off-by: Alison Wang <b18965@freescale.com>
               Xiaochun Li <b41219@freescale.com>
ENGR00180953-2: dspi: update dspi driver support for Vybrid 2012-10-17T18:37:23+00:00 Alison Wang b18965@freescale.com 2012-09-12T07:13:01+00:00 ba9f7d89d3872246f61af0f867fbe7bdadb289ad Update dspi driver support for Vybrid after debugging on board. Signed-off-by: Jason Jin <jason.jin@freescale.com> Alison Wang <b18965@freescale.com> 
Update dspi driver support for Vybrid after debugging on board.

Signed-off-by: Jason Jin <jason.jin@freescale.com>
               Alison Wang <b18965@freescale.com>
ENGR00180953-2: dspi: add dspi driver support for Faraday 2012-09-12T20:49:53+00:00 Alison Wang b18965@freescale.com 2012-07-27T03:31:06+00:00 10d6fbb19dfff064f9d78f8ac50662b999b4e597 Add dspi driver support for Faraday. Signed-off-by: Alison Wang <b18965@freescale.com> 
Add dspi driver support for Faraday.

Signed-off-by: Alison Wang <b18965@freescale.com>
ENGR00157253-2 MX6Q spi: update spi driver for MX6Q 2012-01-09T13:03:30+00:00 Robin Gong B38343@freescale.com 2011-10-28T10:31:40+00:00 7b33cd5fbba7d7b829823084f0d7a2ca08ea611e update spi driver for MX6Q Signed-off-by: Robin Gong <B38343@freescale.com> 
update spi driver for MX6Q
Signed-off-by: Robin Gong <B38343@freescale.com>
ENGR00142020-1: MX50: Add SPI and MC13892 support 2012-01-09T12:08:09+00:00 Ranjani Vaidyanathan ra5478@freescale.com 2011-04-13T16:19:03+00:00 106a29af3c4c1a282252adabd32ce86acac2c10c Add PMIC support for MX50 Signed-off-by: Ranjani Vaidyanathan <ra5478@freescale.com> 
Add PMIC support for MX50

Signed-off-by: Ranjani Vaidyanathan <ra5478@freescale.com>
ENGR00141391-1 PMIC: Add DA9053 source code from Dialog 2012-01-09T11:53:51+00:00 Zhou Jingyu b02241@freescale.com 2011-03-02T07:36:28+00:00 3b91b5ac920ba4e716afb8618ee10d6fb7711852 Add DA9053 original source code Signed-off-by: Zhou Jingyu <Jingyu.Zhou@freescale.com> Acked-by: Lily Zhang <r58066@freescale.com> 
Add DA9053 original source code

Signed-off-by: Zhou Jingyu <Jingyu.Zhou@freescale.com>
Acked-by: Lily Zhang <r58066@freescale.com>
spi/s3c64xx: Bug fix for SPI with different FIFO level 2011-07-06T06:03:08+00:00 Padmavathi Venna padma.v@samsung.com 2011-07-05T08:14:02+00:00 3075741417d47cccc890ed30da9ece666006553a The existing macro fails for following scenarios. 1) S5P64X0 channel 1 2) S5PV210 channel 1 The FIFO data level supported in the above SoCs either 64 or 256 bytes depending on the channel. Because of this the TX_DONE is the 25 bit in the status register. The existing macro works for the following scenarios 1) S3C6410 all channels 2) S5PC100 all channels The FIFO data level supported in the above SoCs 64 bytes on all the channels. Because of this the TX_DONE is the 21 bit in the status register. So when we use the existing macro for the non-working SoCs it is not anding with the TX_DONE bit for transmission status check. Signed-off-by: Padmavathi Venna <padma.v@samsung.com> Acked-by: Jassi Brar <jassisinghbrar@gmail.com> Acked-by: Grant Likely <grant.likely@secretlab.ca> Signed-off-by: Kukjin Kim <kgene.kim@samsung.com> 
The existing macro fails for following scenarios.
1) S5P64X0 channel 1
2) S5PV210 channel 1

The FIFO data level supported in the above SoCs either 64 or
256 bytes depending on the channel. Because of this the TX_DONE
is the 25 bit in the status register.

The existing macro works for the following scenarios
1) S3C6410 all channels
2) S5PC100 all channels

The FIFO data level supported in the above SoCs 64 bytes
on all the channels. Because of this the TX_DONE is the 21 bit
in the status register.

So when we use the existing macro for the non-working SoCs
it is not anding with the TX_DONE bit for transmission status check.

Signed-off-by: Padmavathi Venna <padma.v@samsung.com>
Acked-by: Jassi Brar <jassisinghbrar@gmail.com>
Acked-by: Grant Likely <grant.likely@secretlab.ca>
Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
spi/bfin_spi: fix handling of default bits per word setting 2011-06-17T14:27:27+00:00 Mike Frysinger vapier@gentoo.org 2011-06-17T08:35:37+00:00 e479c60456ef22b0869432887216186aabaed086 The default bits per word setting should be 8 bits, but since most of our devices have been explicitly setting this up, we didn't notice when the default stopped working. At the moment, any default transfers without an explicit bit size setting error out with: bfin-spi bfin-spi.0: transfer: unsupported bits_per_word So in the transfer logic, have a bits_per_word setting of 0 fall into the 8 bit transfer logic. Signed-off-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: Grant Likely <grant.likely@secretlab.ca> 
The default bits per word setting should be 8 bits, but since most of our
devices have been explicitly setting this up, we didn't notice when the
default stopped working.

At the moment, any default transfers without an explicit bit size setting
error out with:
bfin-spi bfin-spi.0: transfer: unsupported bits_per_word

So in the transfer logic, have a bits_per_word setting of 0 fall into the
8 bit transfer logic.

Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
spi-pl022: Add missing return value update 2011-06-13T15:18:45+00:00 Virupax Sadashivpetimath virupax.sadashivpetimath@stericsson.com 2011-06-13T10:53:46+00:00 e3f88ae9960920598cad132c553019ee79ff3aca Return error on out of range cpsdvsr value. Acked-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Virupax Sadashivpetimath <virupax.sadashivpetimath@stericsson.com> Signed-off-by: Grant Likely <grant.likely@secretlab.ca> 
Return error on out of range cpsdvsr value.

Acked-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Virupax Sadashivpetimath <virupax.sadashivpetimath@stericsson.com>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
spi/omap2: fix uninitialized variable 2011-06-03T20:57:07+00:00 Govindraj.R govindraj.raja@ti.com 2011-06-01T06:01:24+00:00 8b20c8cb89b733f5a73fad1f7ad7cff8325e0034 fixes below compilation warning. The variable doesn't actual ever get used uninitialized, but that's no reason to be sloppy. drivers/spi/omap2_mcspi.c: In function 'omap2_mcspi_txrx_dma': drivers/spi/omap2_mcspi.c:301: warning: 'elements' may be used uninitialized in this function Signed-off-by: Govindraj.R <govindraj.raja@ti.com> [grant.likely: amended description] Signed-off-by: Grant Likely <grant.likely@secretlab.ca> 
fixes below compilation warning.  The variable doesn't actual ever get
used uninitialized, but that's no reason to be sloppy.

drivers/spi/omap2_mcspi.c: In function 'omap2_mcspi_txrx_dma':
drivers/spi/omap2_mcspi.c:301: warning: 'elements' may be used uninitialized in this function

Signed-off-by: Govindraj.R <govindraj.raja@ti.com>
[grant.likely: amended description]
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>