From: Thor Thayer <thor.thayer@linux.intel.com>
To: Atsushi Nemoto <atsushi.nemoto@sord.co.jp>, linux-i2c@vger.kernel.org
Cc: tomonori.sakita@sord.co.jp
Subject: Re: [PATCH] i2c: altera: Fix race between xfer_msg and isr thread
Date: Thu, 16 Apr 2020 14:49:40 -0500 [thread overview]
Message-ID: <4f874ee2-3828-047a-78b1-ccbe674c0ff3@linux.intel.com> (raw)
In-Reply-To: <20200410.100640.1949609603287475131.atsushi.nemoto@sord.co.jp>
On 4/9/20 8:06 PM, Atsushi Nemoto wrote:
> Use a mutex to protect access to idev->msg_len, idev->buf, etc. which
> are modified by both altr_i2c_xfer_msg() and altr_i2c_isr().
>
> Signed-off-by: Atsushi Nemoto <atsushi.nemoto@sord.co.jp>
> ---
Acked-by: Thor Thayer <thor.thayer@linux.intel.com>
> drivers/i2c/busses/i2c-altera.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/i2c/busses/i2c-altera.c b/drivers/i2c/busses/i2c-altera.c
> index 20ef63820c77..3db7d77c5a1e 100644
> --- a/drivers/i2c/busses/i2c-altera.c
> +++ b/drivers/i2c/busses/i2c-altera.c
> @@ -70,6 +70,7 @@
> * @isr_mask: cached copy of local ISR enables.
> * @isr_status: cached copy of local ISR status.
> * @lock: spinlock for IRQ synchronization.
> + * @mutex: mutex for IRQ thread.
> */
> struct altr_i2c_dev {
> void __iomem *base;
> @@ -86,6 +87,7 @@ struct altr_i2c_dev {
> u32 isr_mask;
> u32 isr_status;
> spinlock_t lock; /* IRQ synchronization */
> + struct mutex mutex;
> };
>
> static void
> @@ -245,10 +247,11 @@ static irqreturn_t altr_i2c_isr(int irq, void *_dev)
> struct altr_i2c_dev *idev = _dev;
> u32 status = idev->isr_status;
>
> + mutex_lock(&idev->mutex);
> if (!idev->msg) {
> dev_warn(idev->dev, "unexpected interrupt\n");
> altr_i2c_int_clear(idev, ALTR_I2C_ALL_IRQ);
> - return IRQ_HANDLED;
> + goto out;
> }
> read = (idev->msg->flags & I2C_M_RD) != 0;
>
> @@ -301,6 +304,8 @@ static irqreturn_t altr_i2c_isr(int irq, void *_dev)
> complete(&idev->msg_complete);
> dev_dbg(idev->dev, "Message Complete\n");
> }
> +out:
> + mutex_unlock(&idev->mutex);
>
> return IRQ_HANDLED;
> }
> @@ -312,6 +317,7 @@ static int altr_i2c_xfer_msg(struct altr_i2c_dev *idev, struct i2c_msg *msg)
> u32 value;
> u8 addr = i2c_8bit_addr_from_msg(msg);
>
> + mutex_lock(&idev->mutex);
> idev->msg = msg;
> idev->msg_len = msg->len;
> idev->buf = msg->buf;
> @@ -336,6 +342,7 @@ static int altr_i2c_xfer_msg(struct altr_i2c_dev *idev, struct i2c_msg *msg)
> altr_i2c_int_enable(idev, imask, true);
> altr_i2c_fill_tx_fifo(idev);
> }
> + mutex_unlock(&idev->mutex);
>
> time_left = wait_for_completion_timeout(&idev->msg_complete,
> ALTR_I2C_XFER_TIMEOUT);
> @@ -410,6 +417,7 @@ static int altr_i2c_probe(struct platform_device *pdev)
> idev->dev = &pdev->dev;
> init_completion(&idev->msg_complete);
> spin_lock_init(&idev->lock);
> + mutex_init(&idev->mutex);
>
> val = device_property_read_u32(idev->dev, "fifo-size",
> &idev->fifo_size);
>
next prev parent reply other threads:[~2020-04-16 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 1:06 [PATCH] i2c: altera: Fix race between xfer_msg and isr thread Atsushi Nemoto
2020-04-16 19:49 ` Thor Thayer [this message]
2020-04-26 8:30 ` Wolfram Sang
2020-04-26 10:39 ` Atsushi Nemoto
2020-05-08 13:10 ` Atsushi Nemoto
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=4f874ee2-3828-047a-78b1-ccbe674c0ff3@linux.intel.com \
--to=thor.thayer@linux.intel.com \
--cc=atsushi.nemoto@sord.co.jp \
--cc=linux-i2c@vger.kernel.org \
--cc=tomonori.sakita@sord.co.jp \
/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).