From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Syed Nayyar Waris <syednwaris@gmail.com>
Cc: jic23@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/3] counter: 104-quad-8: Add lock guards - differential encoder cable
Date: Fri, 13 Mar 2020 12:51:36 -0400 [thread overview]
Message-ID: <20200313165136.GB5024@icarus> (raw)
In-Reply-To: <20200313120133.GA17830@syed>
[-- Attachment #1: Type: text/plain, Size: 2408 bytes --]
On Fri, Mar 13, 2020 at 05:31:33PM +0530, Syed Nayyar Waris wrote:
> Add lock protection from race conditions in the 104-quad-8 counter
> driver for differential encoder cable status changes. There is no IRQ
> handling so use spin_lock calls for protection.
>
> Fixes: bbef69e088c3 ("counter: 104-quad-8: Support Differential Encoder Cable Status")
>
> Signed-off-by: Syed Nayyar Waris <syednwaris@gmail.com>
Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com>
> ---
> Changes in v4:
> - Shift review-comments section so that it is not saved in commit message.
> - Add spin_unlock calls for deadlock avoidance.
> - Few changes related to casting.
>
> drivers/counter/104-quad-8.c | 18 +++++++++++++++---
> 1 file changed, 15 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/counter/104-quad-8.c b/drivers/counter/104-quad-8.c
> index 9dab190..c9e227f 100644
> --- a/drivers/counter/104-quad-8.c
> +++ b/drivers/counter/104-quad-8.c
> @@ -1151,18 +1151,26 @@ static ssize_t quad8_signal_cable_fault_read(struct counter_device *counter,
> struct counter_signal *signal,
> void *private, char *buf)
> {
> - const struct quad8_iio *const priv = counter->priv;
> + struct quad8_iio *const priv = counter->priv;
> const size_t channel_id = signal->id / 2;
> - const bool disabled = !(priv->cable_fault_enable & BIT(channel_id));
> + bool disabled;
> unsigned int status;
> unsigned int fault;
>
> - if (disabled)
> + spin_lock(&priv->lock);
> +
> + disabled = !(priv->cable_fault_enable & BIT(channel_id));
> +
> + if (disabled) {
> + spin_unlock(&priv->lock);
> return -EINVAL;
> + }
>
> /* Logic 0 = cable fault */
> status = inb(priv->base + QUAD8_DIFF_ENCODER_CABLE_STATUS);
>
> + spin_unlock(&priv->lock);
> +
> /* Mask respective channel and invert logic */
> fault = !(status & BIT(channel_id));
>
> @@ -1194,6 +1202,8 @@ static ssize_t quad8_signal_cable_fault_enable_write(
> if (ret)
> return ret;
>
> + spin_lock(&priv->lock);
> +
> if (enable)
> priv->cable_fault_enable |= BIT(channel_id);
> else
> @@ -1204,6 +1214,8 @@ static ssize_t quad8_signal_cable_fault_enable_write(
>
> outb(cable_fault_enable, priv->base + QUAD8_DIFF_ENCODER_CABLE_STATUS);
>
> + spin_unlock(&priv->lock);
> +
> return len;
> }
>
> --
> 2.7.4
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-03-13 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 12:01 [PATCH v4 2/3] counter: 104-quad-8: Add lock guards - differential encoder cable Syed Nayyar Waris
2020-03-13 16:51 ` William Breathitt Gray [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=20200313165136.GB5024@icarus \
--to=vilhelm.gray@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syednwaris@gmail.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).