From: Quanyang Wang <quanyang.wang@windriver.com>
To: Tudor Ambarus <tudor.ambarus@microchip.com>, <broonie@kernel.org>,
<amit.kumar-mahapatra@xilinx.com>
Cc: <michal.simek@xilinx.com>, <linux-spi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Revert "spi: spi-zynqmp-gqspi: add mutex locking for exec_op"
Date: Wed, 15 Dec 2021 11:06:46 +0800 [thread overview]
Message-ID: <58864ce3-c925-6946-670b-60233b1653a5@windriver.com> (raw)
In-Reply-To: <20211214110152.48316-1-tudor.ambarus@microchip.com>
On 12/14/21 7:01 PM, Tudor Ambarus wrote:
> This reverts commit a0f65be6e880a14d3445b75e7dc03d7d015fc922.
>
> SPIMEM uses ctlr->bus_lock_mutex to prevent concurrency on
> ctlr->mem_ops->exec_op().
>
> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
Reviewed-by: Quanyang Wang <quanyang.wang@windriver.com>
> ---
> drivers/spi/spi-zynqmp-gqspi.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/drivers/spi/spi-zynqmp-gqspi.c b/drivers/spi/spi-zynqmp-gqspi.c
> index 328b6559bb19..189fe4eb59ad 100644
> --- a/drivers/spi/spi-zynqmp-gqspi.c
> +++ b/drivers/spi/spi-zynqmp-gqspi.c
> @@ -174,7 +174,6 @@ struct zynqmp_qspi {
> u32 genfifoentry;
> enum mode_type mode;
> struct completion data_completion;
> - struct mutex op_lock;
> };
>
> /**
> @@ -946,7 +945,6 @@ static int zynqmp_qspi_exec_op(struct spi_mem *mem,
> op->cmd.opcode, op->cmd.buswidth, op->addr.buswidth,
> op->dummy.buswidth, op->data.buswidth);
>
> - mutex_lock(&xqspi->op_lock);
> zynqmp_qspi_config_op(xqspi, mem->spi);
> zynqmp_qspi_chipselect(mem->spi, false);
> genfifoentry |= xqspi->genfifocs;
> @@ -1069,7 +1067,6 @@ static int zynqmp_qspi_exec_op(struct spi_mem *mem,
> return_err:
>
> zynqmp_qspi_chipselect(mem->spi, true);
> - mutex_unlock(&xqspi->op_lock);
>
> return err;
> }
> @@ -1143,8 +1140,6 @@ static int zynqmp_qspi_probe(struct platform_device *pdev)
>
> init_completion(&xqspi->data_completion);
>
> - mutex_init(&xqspi->op_lock);
> -
> pm_runtime_use_autosuspend(&pdev->dev);
> pm_runtime_set_autosuspend_delay(&pdev->dev, SPI_AUTOSUSPEND_TIMEOUT);
> pm_runtime_set_active(&pdev->dev);
>
prev parent reply other threads:[~2021-12-15 3:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 11:01 Tudor Ambarus
2021-12-14 11:01 ` Tudor Ambarus
2021-12-15 3:06 ` Quanyang Wang [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=58864ce3-c925-6946-670b-60233b1653a5@windriver.com \
--to=quanyang.wang@windriver.com \
--cc=amit.kumar-mahapatra@xilinx.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=tudor.ambarus@microchip.com \
/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
all inboxes | Powered by JetHome®