All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Doug Anderson <dianders@chromium.org>
Cc: Naveen Krishna Chatradhi <ch.naveen@samsung.com>,
	linux-iio <linux-iio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-samsung-soc@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Naveen Krishna <naveenkrishna.ch@gmail.com>
Subject: Re: [RFC: PATCH 2/2] iio: adc: exynos_adc: Handle timeout and race conditions
Date: Fri, 05 Apr 2013 18:38:36 +0200	[thread overview]
Message-ID: <515EFE0C.2030401@metafoo.de> (raw)
In-Reply-To: <CAD=FV=XHKn_vqv7-rqpraJy_V2kyBfo98WdMsAJ5eXhADc_rmA@mail.gmail.com>

On 04/05/2013 04:56 PM, Doug Anderson wrote:
> Lars,
> 
> On Fri, Apr 5, 2013 at 1:53 AM, Lars-Peter Clausen <lars@metafoo.de> wrote:
>> Since we sleep inside the protected section we need to use a mutex.
> 
> Ah, good point.
> 
>> It's not the timeout case I'm worried about, but the case where the transfer
>> is interrupted by the user. Even though it is rather unlikely for the
>> problem to occur we should still try to avoid it, this is one of these
>> annoying heisenbugs that happen once in a while and nobody is able to
>> reproduce them.
> 
> Yes, of course.  Then we can also get extra confidence that the reset
> logic works well by stressing out this case...  :)
> 
> This makes me think, though.  Given how fast we expect the ADC
> transaction to finish, would there be any benefit to making the wait
> non-interruptible and then shortening the timeout a whole lot.  If we
> shortened to 1ms then we're really not "non-interruptible" for very
> long and there's less chance of subtle bugs in the way that reset
> works.

Yes, that could also work.

- Lars

  reply	other threads:[~2013-04-05 15:39 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15 16:26 [RFC: PATCH 2/2] iio: adc: exynos_adc: Handle timeout and race conditions Naveen Krishna Chatradhi
2013-03-15 21:53 ` Lars-Peter Clausen
2013-03-15 21:53   ` Lars-Peter Clausen
2013-03-16  0:37   ` Doug Anderson
2013-03-16 14:41     ` Lars-Peter Clausen
2013-03-16 14:41       ` Lars-Peter Clausen
2013-04-03 17:06       ` Doug Anderson
2013-04-03 17:06         ` Doug Anderson
2013-04-05  8:53         ` Lars-Peter Clausen
2013-04-05 14:56           ` Doug Anderson
2013-04-05 14:56             ` Doug Anderson
2013-04-05 16:38             ` Lars-Peter Clausen [this message]
2013-04-04  3:59 ` [PATCH 14/14] temp: iio: adc: exynos_adc: Handle timeout issues Naveen Krishna Chatradhi
2013-04-04  4:09   ` Naveen Krishna Ch
2013-04-04  4:06 ` [PATCH] " Naveen Krishna Chatradhi
2013-04-04  4:06   ` Naveen Krishna Chatradhi
2013-04-13  4:36   ` Naveen Krishna Ch
2013-04-13  4:36     ` Naveen Krishna Ch
2013-04-15 16:01     ` Doug Anderson
2013-04-15 16:01       ` Doug Anderson
2013-05-02 18:01   ` [PATCH v2] " Naveen Krishna Chatradhi
2013-05-02 18:10     ` Tomasz Figa
2013-05-02 18:10       ` Tomasz Figa
2013-05-02 18:22       ` Naveen Krishna Ch
2013-05-02 18:22         ` Naveen Krishna Ch
2013-05-02 18:36         ` Tomasz Figa
2013-05-02 18:36           ` Tomasz Figa
2013-10-11  8:23   ` [PATCH v3] iio: exynos_adc: use wait_for_completion_timeout instead of interruptible Naveen Krishna Chatradhi
2013-10-11 14:30     ` Lars-Peter Clausen
2013-10-11 14:30       ` Lars-Peter Clausen
2013-10-12  6:40       ` Naveen Krishna Ch
2013-10-12  6:40         ` Naveen Krishna Ch
2013-10-15  5:15     ` [PATCH v4] " Naveen Krishna Chatradhi
2013-10-25 15:42       ` Doug Anderson
2013-10-28  5:41     ` [PATCH v5] " Naveen Krishna Chatradhi
2013-11-05  9:45     ` [PATCH v6] " Naveen Krishna Chatradhi
2013-11-10 12:48       ` Tomasz Figa
2013-11-10 12:48         ` Tomasz Figa

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=515EFE0C.2030401@metafoo.de \
    --to=lars@metafoo.de \
    --cc=ch.naveen@samsung.com \
    --cc=dianders@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=naveenkrishna.ch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.