linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c: exynos5: Properly use the "noirq" variants of suspend/resume
Date: Tue, 24 Jun 2014 00:31:37 +0200	[thread overview]
Message-ID: <53A8AAC9.8030407@gmail.com> (raw)
In-Reply-To: <CAD=FV=U0P2kyfnxdU2E1Gm8TdD_cFd6brmtQ7-gpajNJuKmWSA@mail.gmail.com>



On 24.06.2014 00:27, Doug Anderson wrote:
> Kevin,
> 
> On Mon, Jun 23, 2014 at 3:19 PM, Kevin Hilman <khilman@linaro.org> wrote:
>> Doug Anderson <dianders@chromium.org> writes:
>>
>> [...]
>>
>>> On Fri, Jun 20, 2014 at 4:59 PM, Tomasz Figa <tomasz.figa@gmail.com> wrote:
>>>>
>>>> I'm not sure noirq is going to work correctly, at least not with current
>>>> callbacks. I can see a call to clk_prepare_enable() there which needs to
>>>> acquire a mutex.
>>>
>>> Nice catch, thanks!  :)
>>>
>>> OK, looking at that now.  Interestingly this doesn't seem to cause us
>>> problems in our ChromeOS 3.8 tree.  I just tried enabling:
>>>   CONFIG_DEBUG_ATOMIC_SLEEP=y
>>>
>>> ...and confirmed that I got it on right:
>>>
>>> # zgrep -i atomic /proc/config.gz
>>> CONFIG_DEBUG_ATOMIC_SLEEP=y
>>>
>>> I can suspend/resume with no problems.  My bet is that it works fine because:
>>>
>>> * resume_noirq is not considered "atomic" in the sense enforced by
>>> CONFIG_DEBUG_ATOMIC_SLEEP (at least not in 3.8--I haven't tried on
>>> ToT)
>>
>> The reason is because "noirq" in the suspend/resume path actually means
>> no *device* IRQs for that specific device.
>>
>> It's often assumed that the "noirq" callbacks are called with *all*
>> interrupts disabled, but that's not the case.  Only the IRQs for that
>> specific device are disabled when its noirq callbacks run.
> 
> Ah, so even with my fix of moving to noirq we could still be broken if
> the system decided to enable interrupts for the device before the i2c
> controller get resumed then we'd still be SOL.
> 
> ...oh, but if it matches probe order then maybe we're guaranteed for
> that not to happen?  We know that we will probe the i2c bus before the
> devices on it, right?

If the mentioned device is a child of the I2C controller then the
parent-child relation determines the order. Otherwise (e.g. another,
non-I2C interrupt source that just triggers some operation on an I2C
device like voltage regulator) we're doomed. ;)

Best regards,
Tomasz

  reply	other threads:[~2014-06-23 22:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19  5:21 [PATCH] i2c: exynos5: Properly use the "noirq" variants of suspend/resume Doug Anderson
2014-06-19 18:43 ` Kevin Hilman
2014-06-19 22:43   ` Doug Anderson
2014-06-20 21:48     ` Kevin Hilman
2014-06-20 22:05       ` Doug Anderson
2014-06-20 23:13         ` Kevin Hilman
2014-06-20 23:53           ` Doug Anderson
2014-06-20 23:59             ` Tomasz Figa
2014-06-23 22:01               ` Doug Anderson
2014-06-23 22:19                 ` Kevin Hilman
2014-06-23 22:24                   ` Tomasz Figa
2014-06-23 22:27                   ` Doug Anderson
2014-06-23 22:31                     ` Tomasz Figa [this message]
2014-06-23 22:46                       ` Doug Anderson
2014-06-23 23:35                       ` Kevin Hilman
2014-06-23 22:23             ` Kevin Hilman
2014-06-23 22:42               ` Doug Anderson
2014-06-23 23:31                 ` Kevin Hilman

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=53A8AAC9.8030407@gmail.com \
    --to=tomasz.figa@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).