Re: [PATCH] spi: core: make zero length transfer valid again

2014-03-03 Thread Thierry Reding
On Fri, Feb 28, 2014 at 11:03:16PM +0900, Atsushi Nemoto wrote: > Zero length transfer becomes invalid since > "spi: core: Validate length of the transfers in message" commit, > but it should be valid to support an odd device, for example, which > requires long delay between chipselect and the

Re: [PATCH] spi: core: make zero length transfer valid again

2014-03-03 Thread Thierry Reding
On Fri, Feb 28, 2014 at 11:03:16PM +0900, Atsushi Nemoto wrote: Zero length transfer becomes invalid since spi: core: Validate length of the transfers in message commit, but it should be valid to support an odd device, for example, which requires long delay between chipselect and the first

Re: [PATCH] spi: core: make zero length transfer valid again

2014-03-02 Thread Mark Brown
On Sat, Mar 01, 2014 at 12:40:39PM +0100, Martin Sperl wrote: > I am not sure if it might make some bus-drivers more complicated > /inefficient just to support this zero length. For most of them it should be relatively straightforward, especially as we factor things out into the core so that the

Re: [PATCH] spi: core: make zero length transfer valid again

2014-03-02 Thread Mark Brown
On Sat, Mar 01, 2014 at 12:40:39PM +0100, Martin Sperl wrote: I am not sure if it might make some bus-drivers more complicated /inefficient just to support this zero length. For most of them it should be relatively straightforward, especially as we factor things out into the core so that the

Re: [PATCH] spi: core: make zero length transfer valid again

2014-03-01 Thread Martin Sperl
On 01.03.2014, at 05:13, Mark Brown wrote: > On Fri, Feb 28, 2014 at 11:03:16PM +0900, Atsushi Nemoto wrote: >> Zero length transfer becomes invalid since >> "spi: core: Validate length of the transfers in message" commit, >> but it should be valid to support an odd device, for example, which >>

Re: [PATCH] spi: core: make zero length transfer valid again

2014-03-01 Thread Martin Sperl
On 01.03.2014, at 05:13, Mark Brown broo...@kernel.org wrote: On Fri, Feb 28, 2014 at 11:03:16PM +0900, Atsushi Nemoto wrote: Zero length transfer becomes invalid since spi: core: Validate length of the transfers in message commit, but it should be valid to support an odd device, for example,

Re: [PATCH] spi: core: make zero length transfer valid again

2014-02-28 Thread Mark Brown
On Fri, Feb 28, 2014 at 11:03:16PM +0900, Atsushi Nemoto wrote: > Zero length transfer becomes invalid since > "spi: core: Validate length of the transfers in message" commit, > but it should be valid to support an odd device, for example, which > requires long delay between chipselect and the

[PATCH] spi: core: make zero length transfer valid again

2014-02-28 Thread Atsushi Nemoto
Zero length transfer becomes invalid since "spi: core: Validate length of the transfers in message" commit, but it should be valid to support an odd device, for example, which requires long delay between chipselect and the first transfer, etc. Signed-off-by: Atsushi Nemoto --- drivers/spi/spi.c

[PATCH] spi: core: make zero length transfer valid again

2014-02-28 Thread Atsushi Nemoto
Zero length transfer becomes invalid since spi: core: Validate length of the transfers in message commit, but it should be valid to support an odd device, for example, which requires long delay between chipselect and the first transfer, etc. Signed-off-by: Atsushi Nemoto an...@mba.ocn.ne.jp ---

Re: [PATCH] spi: core: make zero length transfer valid again

2014-02-28 Thread Mark Brown
On Fri, Feb 28, 2014 at 11:03:16PM +0900, Atsushi Nemoto wrote: Zero length transfer becomes invalid since spi: core: Validate length of the transfers in message commit, but it should be valid to support an odd device, for example, which requires long delay between chipselect and the first