Re: [PATCH 4.3 041/200] spi: omap2-mcspi: disable other channels CHCONF_FORCE in prepare_message

[Greg Kroah-Hartman]

On Sun, Feb 14, 2016 at 09:08:50PM -0600, Michael Welling wrote:
> On Sun, Feb 14, 2016 at 03:17:36PM -0800, Greg Kroah-Hartman wrote:
> > On Sun, Feb 14, 2016 at 04:50:47PM -0600, Michael Welling wrote:
> > > On Sun, Feb 14, 2016 at 02:20:48PM -0800, Greg Kroah-Hartman wrote:
> > > > 4.3-stable review patch.  If anyone has any objections, please let me know.
> > > >
> > > 
> > > If not planned it should be considered that we include the latest two
> > > commits to spi-omap2-mcpsi into stable as well.
> > > 
> > > spi: omap2-mcspi: Prevent duplicate gpio_request
> > > spi: omap2-mcspi: Add calls for pinctrl state select 
> > > 
> > > Let me know if I need to do anything to make this happen.
> > 
> > What are the git commit ids of them?
> 
> commit 2f538c017e1a8620d19553931199c6d6a6d31bb2
> Author: Michael Welling <mwelling@xxxxxxxx>
> Date:   Mon Nov 30 09:02:39 2015 -0600
> 
>     spi: omap2-mcspi: Prevent duplicate gpio_request
>     
>     Occasionally the setup function will be called multiple times. Only request
>     the gpio the first time otherwise -EBUSY will occur on subsequent calls to
>     setup.
>     
>     Reported-by: Joseph Bell <joe@xxxxxxxxxxxx>
>     
>     Signed-off-by: Michael Welling <mwelling@xxxxxxxx>
>     Signed-off-by: Mark Brown <broonie@xxxxxxxxxx>

That seems reasonable but:

> commit beca365565d8f8912dce67567f54ad4c71734843
> Author: Pascal Huerst <pascal.huerst@xxxxxxxxx>
> Date:   Thu Nov 19 16:18:28 2015 +0100
> 
>     spi: omap2-mcspi: Add calls for pinctrl state select
>     
>     This adds calls to pinctrl subsystem in order to switch pin states
>     on suspend/resume if you provide a "sleep" state in DT.
>     
>     If no "sleep" state is provided in DT, these calls turn
>     to NOPs.
>     
>     Signed-off-by: Pascal Huerst <pascal.huerst@xxxxxxxxx>
>     Signed-off-by: Mark Brown <broonie@xxxxxxxxxx>

That looks like a new feature being added.

> > What stable tree(s) do you want
> > them applied to?
> 
> v4.3, v4.4

4.3 is now end-of-life with this release, can you live with these just
in 4.4-stable instead?

thanks,

greg k-h