linux.git/drivers/spi/spi-loopback-test.c, branch v4.12

Merge remote-tracking branches 'spi/topic/spidev', 'spi/topic/spidev-test', 'spi/topic/sunxi', 'spi/topic/tegra' and 'spi/topic/test' into spi-next

2017-04-26T14:58:16+00:00

spi: loopback-test: fix spelling mistake: "minimam" -> "minimum"

2017-03-30T10:15:53+00:00

trivial fix to spelling mistake in dev_err error message

Signed-off-by: Colin Ian King 
Signed-off-by: Mark Brown

spi: loopback-test: fix potential integer overflow on multiple

2017-03-20T16:11:39+00:00

A multiplication of 8U * xfer-len with the type of a 32 bit unsigned int
is evaluated using 32 bit arithmetic and then used in a context that
expects an expression of type unsigned long long (64 bits).  Avoid any
potential overflow by casting BITS_PER_BYTE to unsigned long long.

Detected by CoverityScan, CID#1419691 ("Unintentional integer overflow")

Fixes: ea9936f324356 ("spi: loopback-test: add elapsed time check")
Signed-off-by: Colin Ian King 
Signed-off-by: Mark Brown

spi: loopback-test: add test spi_message with delay after transfers

2017-03-17T21:54:12+00:00

This adds a new test to check whether the spi_transfer.delay_usecs
setting has properly taken effect.

Signed-off-by: Akinobu Mita 
Signed-off-by: Mark Brown

spi: loopback-test: add elapsed time check

2017-03-17T21:54:08+00:00

This adds checks whether the elapsed time is longer than the minimam
estimated time.  The estimated time is calculated with the total
transfer length per clock rate and optional spi_transfer.delay_usecs.

Signed-off-by: Akinobu Mita 
Signed-off-by: Mark Brown

spi: loopback-test: add ability to test zero-length transfer

2017-03-17T21:54:00+00:00

The spi-loopback-test module currently cannot test the spi_message
including a zero-length transfer.  Because the zero-length transfer is
treated as a special value in several meanings.

1. The number of spi_transfer to execute in one test case is described
by spi_test.transfer_count.  It is normally computed by counting number
of transfers with len > 0 in spi_test.transfers array.

This change stops the detection for the number of spi_transfer.  Each
spi_test.transfer_count needs to be filled by hand now.

2. The spi_test.iterate_len is a list of transfer length to iterate on.
This list is terminated by zero, so zero-length transfer cannot be
included.

This changes the terminal value from 0 to -1.

3. The length for the spi_transfer masked by spi_test.iterate_transfer_mask
is iterated.  Before starting the iteration, the default value which
is statically initialized is applied.  In order to specify the default
value, zero-length is reserved.

Currently, the default values are always '1'.  So this removes this
trick and add '1' to iterate_len list.

By applying all these changes, the spi-loopback-test can execute spi
messages with zero-length transfer.

Signed-off-by: Akinobu Mita 
Signed-off-by: Mark Brown

spi: loopback-test: don't skip comparing the first byte of rx_buf

2017-03-17T21:53:56+00:00

When the loopback parameter is set, rx_buf are compared with tx_buf
after the spi_message is executed.  But the first byte of buffer is
not checked.

Signed-off-by: Akinobu Mita 
Signed-off-by: Mark Brown

spi: loopback-test: correct mismatched test description and configuration

2017-03-17T21:53:53+00:00

The test "two tx-transfers - alter first" actually alters the second
not the first transfer.  Similarly the test "two tx-transfers - alter
second" actually alters the first not the second transfer.

The mismatches for the two symmetrical tests cancel each other's
mistakes.  But it's better to fix the mismatches to avoid confusion.

Signed-off-by: Akinobu Mita 
Signed-off-by: Mark Brown

spi: loopback-test: fix compile error on x86

2017-03-17T13:06:12+00:00

Fix compile error caused by missing vmalloc() definition
on x86 (and maybe other platforms) by including vmalloc.h.

Signed-off-by: Frode Isaksen 
Signed-off-by: Mark Brown

spi: loopback-test: add option to use vmalloc'ed buffers

2017-03-15T19:35:53+00:00

Using vmalloc'ed buffers will use one SG entry for each page,
that may provoke DMA errors for large transfers.
Also vmalloc'ed buffers may cause errors on CPU's with VIVT cache.
Add this option to catch these errors when testing.
Note that to catch VIVT cache errors, checking the rx range
has to be disabled, so this option has been added as well.

Signed-off-by: Frode Isaksen 
Signed-off-by: Mark Brown