Re: [PATCH v2] spi: omap2-mcspi: disable other channels CHCONF_FORCE in prepare_message

2015-10-09 Thread Michael Welling
On Fri, Oct 09, 2015 at 05:29:26PM +0200, Neil Armstrong wrote: > On 10/09/2015 05:26 PM, Michael Welling wrote: > > On Fri, Oct 09, 2015 at 03:47:41PM +0200, Neil Armstrong wrote: > >> Since the "Switch driver to use transfer_one" change, the cs_change > >> behavior has changed and a channel chip

Re: [PATCH v2] spi: omap2-mcspi: disable other channels CHCONF_FORCE in prepare_message

2015-10-09 Thread Neil Armstrong
On 10/09/2015 05:26 PM, Michael Welling wrote: > On Fri, Oct 09, 2015 at 03:47:41PM +0200, Neil Armstrong wrote: >> Since the "Switch driver to use transfer_one" change, the cs_change >> behavior has changed and a channel chip select can still be >> asserted when changing channel from a previous la

Re: [PATCH v2] spi: omap2-mcspi: disable other channels CHCONF_FORCE in prepare_message

2015-10-09 Thread Michael Welling
On Fri, Oct 09, 2015 at 03:47:41PM +0200, Neil Armstrong wrote: > Since the "Switch driver to use transfer_one" change, the cs_change > behavior has changed and a channel chip select can still be > asserted when changing channel from a previous last transfer in a > message having the cs_change attr

[PATCH v2] spi: omap2-mcspi: disable other channels CHCONF_FORCE in prepare_message

2015-10-09 Thread Neil Armstrong
Since the "Switch driver to use transfer_one" change, the cs_change behavior has changed and a channel chip select can still be asserted when changing channel from a previous last transfer in a message having the cs_change attribute. Since there is no sense having multiple chip select being assert