From: Michael Welling <mwelling@ieee.org>
To: gregkh@linuxfoundation.org
Cc: broonie@kernel.org, joe@iachieved.it, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "spi: omap2-mcspi: Prevent duplicate gpio_request" has been added to the 4.4-stable tree
Date: Tue, 1 Mar 2016 10:58:45 -0600 [thread overview]
Message-ID: <20160301165845.GA10446@deathstar> (raw)
In-Reply-To: <145681421486243@kroah.com>
On Tue, Mar 01, 2016 at 08:15:27AM +0000, gregkh@linuxfoundation.org wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> spi: omap2-mcspi: Prevent duplicate gpio_request
>
> to the 4.4-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
Thanks Greg.
> The filename of the patch is:
> spi-omap2-mcspi-prevent-duplicate-gpio_request.patch
> and it can be found in the queue-4.4 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
>
>
> From 2f538c017e1a8620d19553931199c6d6a6d31bb2 Mon Sep 17 00:00:00 2001
> From: Michael Welling <mwelling@ieee.org>
> Date: Mon, 30 Nov 2015 09:02:39 -0600
> Subject: spi: omap2-mcspi: Prevent duplicate gpio_request
>
> From: Michael Welling <mwelling@ieee.org>
>
> commit 2f538c017e1a8620d19553931199c6d6a6d31bb2 upstream.
>
> 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@iachieved.it>
>
> Signed-off-by: Michael Welling <mwelling@ieee.org>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> ---
> drivers/spi/spi-omap2-mcspi.c | 19 ++++++++++---------
> 1 file changed, 10 insertions(+), 9 deletions(-)
>
> --- a/drivers/spi/spi-omap2-mcspi.c
> +++ b/drivers/spi/spi-omap2-mcspi.c
> @@ -1024,6 +1024,16 @@ static int omap2_mcspi_setup(struct spi_
> spi->controller_state = cs;
> /* Link this to context save list */
> list_add_tail(&cs->node, &ctx->cs);
> +
> + if (gpio_is_valid(spi->cs_gpio)) {
> + ret = gpio_request(spi->cs_gpio, dev_name(&spi->dev));
> + if (ret) {
> + dev_err(&spi->dev, "failed to request gpio\n");
> + return ret;
> + }
> + gpio_direction_output(spi->cs_gpio,
> + !(spi->mode & SPI_CS_HIGH));
> + }
> }
>
> if (!mcspi_dma->dma_rx || !mcspi_dma->dma_tx) {
> @@ -1032,15 +1042,6 @@ static int omap2_mcspi_setup(struct spi_
> return ret;
> }
>
> - if (gpio_is_valid(spi->cs_gpio)) {
> - ret = gpio_request(spi->cs_gpio, dev_name(&spi->dev));
> - if (ret) {
> - dev_err(&spi->dev, "failed to request gpio\n");
> - return ret;
> - }
> - gpio_direction_output(spi->cs_gpio, !(spi->mode & SPI_CS_HIGH));
> - }
> -
> ret = pm_runtime_get_sync(mcspi->dev);
> if (ret < 0)
> return ret;
>
>
> Patches currently in stable-queue which might be from mwelling@ieee.org are
>
> queue-4.4/spi-omap2-mcspi-prevent-duplicate-gpio_request.patch
prev parent reply other threads:[~2016-03-01 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 8:15 Patch "spi: omap2-mcspi: Prevent duplicate gpio_request" has been added to the 4.4-stable tree gregkh
2016-03-01 16:58 ` Michael Welling [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160301165845.GA10446@deathstar \
--to=mwelling@ieee.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@iachieved.it \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).