From: Tom Rix <trix@redhat.com>
To: Li-hao Kuo <lhjeff911@gmail.com>,
broonie@kernel.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: wells.lu@sunplus.com, lh.kuo@sunplus.com, nathan@kernel.org
Subject: Re: [PATCH] spi: remove spin_lock_irq in the irq procress
Date: Wed, 13 Apr 2022 04:45:33 -0700 [thread overview]
Message-ID: <fdb1e0a6-62f9-c0a3-c1db-8857087701a1@redhat.com> (raw)
In-Reply-To: <9e12d806c5554b4ed18c644f71f6662fcf0d0516.1649813822.git.lhjeff911@gmail.com>
On 4/12/22 6:38 PM, Li-hao Kuo wrote:
> - remove spin_lock_irq and spin_unlock_irq in the irq funciton
function
I was expecting a statement on why is the lock is not needed.
Could you add one ?
Tom
>
> Signed-off-by: Li-hao Kuo <lhjeff911@gmail.com>
> ---
> drivers/spi/spi-sunplus-sp7021.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/spi/spi-sunplus-sp7021.c b/drivers/spi/spi-sunplus-sp7021.c
> index f989f7b..120623c 100644
> --- a/drivers/spi/spi-sunplus-sp7021.c
> +++ b/drivers/spi/spi-sunplus-sp7021.c
> @@ -199,8 +199,6 @@ static irqreturn_t sp7021_spi_master_irq(int irq, void *dev)
> if (tx_len == 0 && total_len == 0)
> return IRQ_NONE;
>
> - spin_lock_irq(&pspim->lock);
> -
> rx_cnt = FIELD_GET(SP7021_RX_CNT_MASK, fd_status);
> if (fd_status & SP7021_RX_FULL_FLAG)
> rx_cnt = pspim->data_unit;
> @@ -239,7 +237,7 @@ static irqreturn_t sp7021_spi_master_irq(int irq, void *dev)
>
> if (isrdone)
> complete(&pspim->isr_done);
> - spin_unlock_irq(&pspim->lock);
> +
> return IRQ_HANDLED;
> }
>
next prev parent reply other threads:[~2022-04-13 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 1:38 [PATCH] spi: remove spin_lock_irq in the irq procress Li-hao Kuo
2022-04-13 11:32 ` Mark Brown
2022-04-14 13:18 ` 郭力豪
2022-04-13 11:45 ` Tom Rix [this message]
2022-04-14 13:16 ` 郭力豪
2022-04-16 15:49 ` Tom Rix
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=fdb1e0a6-62f9-c0a3-c1db-8857087701a1@redhat.com \
--to=trix@redhat.com \
--cc=broonie@kernel.org \
--cc=lh.kuo@sunplus.com \
--cc=lhjeff911@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=wells.lu@sunplus.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;
as well as URLs for NNTP newsgroup(s).