<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/spi, branch v3.1</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v3.1</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v3.1'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2011-10-04T16:10:50Z</updated>
<entry>
<title>spi-topcliff-pch: Fix overrun issue</title>
<updated>2011-10-04T16:10:50Z</updated>
<author>
<name>Tomoya MORINAGA</name>
<email>tomoya-linux@dsn.okisemi.com</email>
</author>
<published>2011-09-06T08:16:38Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f3e03e2eb0bcd9266720695b82a523e6bc526ff7'/>
<id>urn:sha1:f3e03e2eb0bcd9266720695b82a523e6bc526ff7</id>
<content type='text'>
We found that adding load, Rx data sometimes drops.(with DMA transfer mode)
The cause is that before starting Rx-DMA processing, Tx-DMA processing starts.
This causes FIFO overrun occurs.

This patch fixes the issue by modifying FIFO tx-threshold and DMA descriptor
size like below.

                      Current                   this patch
Rx-descriptor   4Byte+12Byte*341    --&gt;    12Byte*340-4Byte-12Byte
Rx-threshold                   (Not modified)
Tx-descriptor   4Byte+12Byte*341    --&gt;    16Byte-12Byte*340
Rx-threshold    12Byte              --&gt;    2Byte

Signed-off-by: Tomoya MORINAGA &lt;tomoya-linux@dsn.okisemi.com&gt;
Signed-off-by: Grant Likely &lt;grant.likely@secretlab.ca&gt;
</content>
</entry>
<entry>
<title>spi-topcliff-pch: Add recovery processing in case FIFO overrun error occurs</title>
<updated>2011-10-04T16:10:50Z</updated>
<author>
<name>Tomoya MORINAGA</name>
<email>tomoya-linux@dsn.okisemi.com</email>
</author>
<published>2011-09-06T08:16:37Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=25e803f9c339a070cd7361e853aebde11b1f9217'/>
<id>urn:sha1:25e803f9c339a070cd7361e853aebde11b1f9217</id>
<content type='text'>
Add recovery processing in case FIFO overrun error occurs with DMA transfer mode.

Signed-off-by: Tomoya MORINAGA &lt;tomoya-linux@dsn.okisemi.com&gt;
Signed-off-by: Grant Likely &lt;grant.likely@secretlab.ca&gt;
</content>
</entry>
<entry>
<title>spi-topcliff-pch: Fix CPU read complete condition issue</title>
<updated>2011-10-04T16:10:50Z</updated>
<author>
<name>Tomoya MORINAGA</name>
<email>tomoya-linux@dsn.okisemi.com</email>
</author>
<published>2011-09-06T08:16:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=373b0eb64b9c97a14720896dcfdebfa3268b1991'/>
<id>urn:sha1:373b0eb64b9c97a14720896dcfdebfa3268b1991</id>
<content type='text'>
We found Rx data sometimes drops.(with non-DMA transfer mode)
The cause is read complete condition is not true.

This patch fixes the issue.

Signed-off-by: Tomoya MORINAGA &lt;tomoya-linux@dsn.okisemi.com&gt;
Signed-off-by: Grant Likely &lt;grant.likely@secretlab.ca&gt;
</content>
</entry>
<entry>
<title>spi-topcliff-pch: Fix SSN Control issue</title>
<updated>2011-10-04T16:10:50Z</updated>
<author>
<name>Tomoya MORINAGA</name>
<email>tomoya-linux@dsn.okisemi.com</email>
</author>
<published>2011-09-06T08:16:35Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=8b7aa961a815dad389525dcd1c36a44c249b1760'/>
<id>urn:sha1:8b7aa961a815dad389525dcd1c36a44c249b1760</id>
<content type='text'>
During processing 1 command/data series,
SSN should keep LOW.
However, currently, SSN becomes HIGH.
This patch fixes the issue.

Signed-off-by: Tomoya MORINAGA &lt;tomoya-linux@dsn.okisemi.com&gt;
Signed-off-by: Grant Likely &lt;grant.likely@secretlab.ca&gt;
</content>
</entry>
<entry>
<title>spi-topcliff-pch: add tx-memory clear after complete transmitting</title>
<updated>2011-10-04T16:10:50Z</updated>
<author>
<name>Tomoya MORINAGA</name>
<email>tomoya-linux@dsn.okisemi.com</email>
</author>
<published>2011-09-06T08:16:34Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=27504be5c10bdc61761ec0126b3645428598ad91'/>
<id>urn:sha1:27504be5c10bdc61761ec0126b3645428598ad91</id>
<content type='text'>
Currently, in case of reading date from SPI flash,
command is sent twice.
The cause is that tx-memory clear processing is missing .
This patch adds the tx-momory clear processing.

Signed-off-by: Tomoya MORINAGA &lt;tomoya-linux@dsn.okisemi.com&gt;
Signed-off-by: Grant Likely &lt;grant.likely@secretlab.ca&gt;
</content>
</entry>
<entry>
<title>spi: Fix WARN when removing spi-fsl-spi module</title>
<updated>2011-09-23T23:28:29Z</updated>
<author>
<name>Jeff Harris</name>
<email>jeff_harris@kentrox.com</email>
</author>
<published>2011-09-23T15:49:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=387719c2ec995019e0af0dc537ca17c9ebd5b64f'/>
<id>urn:sha1:387719c2ec995019e0af0dc537ca17c9ebd5b64f</id>
<content type='text'>
If CPM mode is not used, the fsl_dummy_rx variable is never allocated.  When
the cleanup attempts to free it, the reference count is zero and a WARN is
generated.  The same CPM mode check used in the initialize is applied to the
free as well.

Tested on 2.6.33 with the previous spi_mpc8xxx driver.  The renamed
spi-fsl-spi driver looks to have the same problem.

Signed-off-by: Jeff Harris &lt;jeff_harris@kentrox.com&gt;
Signed-off-by: Grant Likely &lt;grant.likely@secretlab.ca&gt;
</content>
</entry>
<entry>
<title>spi/imx: Fix spi-imx when the hardware SPI chipselects are used</title>
<updated>2011-09-15T21:54:38Z</updated>
<author>
<name>Fabio Estevam</name>
<email>fabio.estevam@freescale.com</email>
</author>
<published>2011-09-15T20:21:15Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=4cc122ac913dbd662403a4a173c41e0d59ab5bdd'/>
<id>urn:sha1:4cc122ac913dbd662403a4a173c41e0d59ab5bdd</id>
<content type='text'>
commit 22a85e4cd51 (spi/imx: add device tree probe support) broke spi-imx usage
when the SPI chipselect is the one internal to the controller.

On a mx31pdk board the following error is seen:

Registering mxc_nand as whole device
------------[ cut here ]------------
WARNING: at drivers/gpio/gpiolib.c:101 gpio_ensure_requested+0x4c/0xf4()
autorequest GPIO-0
Modules linked in:
[&lt;c0014410&gt;] (unwind_backtrace+0x0/0xf4) from [&lt;c0025754&gt;] (warn_slowpath_common+0x4c/0x64)
[&lt;c0025754&gt;] (warn_slowpath_common+0x4c/0x64) from [&lt;c0025800&gt;] (warn_slowpath_fmt+0x30/0x40)
[&lt;c0025800&gt;] (warn_slowpath_fmt+0x30/0x40) from [&lt;c0198688&gt;] (gpio_ensure_requested+0x4c/0xf4)
[&lt;c0198688&gt;] (gpio_ensure_requested+0x4c/0xf4) from [&lt;c01988c8&gt;] (gpio_direction_output+0xa0/0x138)
[&lt;c01988c8&gt;] (gpio_direction_output+0xa0/0x138) from [&lt;c01ed198&gt;] (spi_imx_setup+0x38/0x4c)
[&lt;c01ed198&gt;] (spi_imx_setup+0x38/0x4c) from [&lt;c01eb5d0&gt;] (spi_setup+0x38/0x50)
[&lt;c01eb5d0&gt;] (spi_setup+0x38/0x50) from [&lt;c01eb85c&gt;] (spi_add_device+0x94/0x124)
[&lt;c01eb85c&gt;] (spi_add_device+0x94/0x124) from [&lt;c01eb960&gt;] (spi_new_device+0x74/0xac)
[&lt;c01eb960&gt;] (spi_new_device+0x74/0xac) from [&lt;c01eb9b8&gt;] (spi_match_master_to_boardinfo+0x20/0x40)
[&lt;c01eb9b8&gt;] (spi_match_master_to_boardinfo+0x20/0x40) from [&lt;c01eba88&gt;] (spi_register_master+0xb0/0x104)
[&lt;c01eba88&gt;] (spi_register_master+0xb0/0x104) from [&lt;c01ec0b4&gt;] (spi_bitbang_start+0x104/0x17c)
[&lt;c01ec0b4&gt;] (spi_bitbang_start+0x104/0x17c) from [&lt;c02c2c4c&gt;] (spi_imx_probe+0x2fc/0x404)
[&lt;c02c2c4c&gt;] (spi_imx_probe+0x2fc/0x404) from [&lt;c01c2498&gt;] (platform_drv_probe+0x18/0x1c)
[&lt;c01c2498&gt;] (platform_drv_probe+0x18/0x1c) from [&lt;c01c1058&gt;] (driver_probe_device+0x78/0x174)
[&lt;c01c1058&gt;] (driver_probe_device+0x78/0x174) from [&lt;c01c11e0&gt;] (__driver_attach+0x8c/0x90)
[&lt;c01c11e0&gt;] (__driver_attach+0x8c/0x90) from [&lt;c01c0860&gt;] (bus_for_each_dev+0x60/0x8c)
[&lt;c01c0860&gt;] (bus_for_each_dev+0x60/0x8c) from [&lt;c01c0088&gt;] (bus_add_driver+0xa0/0x288)
[&lt;c01c0088&gt;] (bus_add_driver+0xa0/0x288) from [&lt;c01c179c&gt;] (driver_register+0x78/0x18c)
[&lt;c01c179c&gt;] (driver_register+0x78/0x18c) from [&lt;c0008490&gt;] (do_one_initcall+0x34/0x178)
[&lt;c0008490&gt;] (do_one_initcall+0x34/0x178) from [&lt;c03a5204&gt;] (kernel_init+0x74/0x118)
[&lt;c03a5204&gt;] (kernel_init+0x74/0x118) from [&lt;c000f65c&gt;] (kernel_thread_exit+0x0/0x8)
---[ end trace 759f924b30fd5a44 ]---

Fix this issue by using the original chip select logic and make spi-imx to work again.

Tested on a mx31pdk that uses the hardware SPI chipselect pins and also
on a mx27pdk that uses GPIO as SPI chipselect.

Signed-off-by: Fabio Estevam &lt;fabio.estevam@freescale.com&gt;
Signed-off-by: Grant Likely &lt;grant.likely@secretlab.ca&gt;
</content>
</entry>
<entry>
<title>spi/pl022: remove function cannot exit</title>
<updated>2011-08-02T13:54:11Z</updated>
<author>
<name>Linus Walleij</name>
<email>linus.walleij@linaro.org</email>
</author>
<published>2011-08-02T09:29:24Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=50658b6602dad6dc76c226917f5d8cec0f680eab'/>
<id>urn:sha1:50658b6602dad6dc76c226917f5d8cec0f680eab</id>
<content type='text'>
The remove function in the PL022 driver cannot abort the remove
function any way, so restructure the code so as not to make that
assumption. Remove will now proceed no matter whether it can
stop the transfer queue or not.

Reported-by: Russell King &lt;linux@arm.linux.org.uk&gt;
Signed-off-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;
Signed-off-by: Grant Likely &lt;grant.likely@secretlab.ca&gt;
</content>
</entry>
<entry>
<title>Merge branch 'spi/next' of git://git.secretlab.ca/git/linux-2.6</title>
<updated>2011-07-22T21:52:44Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2011-07-22T21:52:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=7235dd74a4733d4b3651349b5261d2e06996427d'/>
<id>urn:sha1:7235dd74a4733d4b3651349b5261d2e06996427d</id>
<content type='text'>
* 'spi/next' of git://git.secretlab.ca/git/linux-2.6: (34 commits)
  spi/imx: add device tree probe support
  spi/imx: copy gpio number passed by platform data into driver private data
  spi/imx: use soc name in spi device type naming scheme
  spi/imx: merge type SPI_IMX_VER_0_7 into SPI_IMX_VER_0_4
  spi/imx: do not use spi_imx2_3 to name SPI_IMX_VER_2_3 function and macro
  spi/imx: use mx21 to name SPI_IMX_VER_0_0 function and macro
  spi/imx: do not make copy of spi_imx_devtype_data
  spi/dw: Add spi number into spi irq desc
  spi/tegra: Use engineering names in DT compatible property
  spi/fsl_spi: fix CPM spi driver
  mach-s3c2410: remove unused spi-gpio.h file
  spi: remove obsolete spi-s3c24xx-gpio driver
  mach-gta2: remove unused spi-gpio.h include
  mach-qt2410: convert to spi_gpio
  mach-jive: convert to spi_gpio
  spi/pxa2xx: Remove unavailable ssp_type from documentation
  spi/bfin_spi: uninline fat queue funcs
  spi/bfin_spi: constify pin array
  spi/bfin_spi: use structs for accessing hardware regs
  spi/topcliff-pch: Support new device ML7223 IOH
  ...

Fix up trivial conflict in arch/arm/mach-ep93xx/Makefile
</content>
</entry>
<entry>
<title>spi/imx: add device tree probe support</title>
<updated>2011-07-14T19:47:18Z</updated>
<author>
<name>Shawn Guo</name>
<email>shawn.guo@linaro.org</email>
</author>
<published>2011-07-09T17:16:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=22a85e4cd51b49ec99703ddfdff8686d5442a093'/>
<id>urn:sha1:22a85e4cd51b49ec99703ddfdff8686d5442a093</id>
<content type='text'>
It adds device tree probe support for spi-imx driver.

Signed-off-by: Shawn Guo &lt;shawn.guo@linaro.org&gt;
Cc: Grant Likely &lt;grant.likely@secretlab.ca&gt;
Signed-off-by: Grant Likely &lt;grant.likely@secretlab.ca&gt;
</content>
</entry>
</feed>
