From: javier.martin@vista-silicon.com (javier Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [dmaengine] [Q] jiffies value does not increase in dma_sync_wait()
Date: Fri, 3 Feb 2012 10:43:02 +0100 [thread overview]
Message-ID: <CACKLOr0sDkaEFFCaby6H1h3hofxJdDbr4LXaFMebGWZ-46EwiQ@mail.gmail.com> (raw)
In-Reply-To: <20120203092456.GJ889@n2100.arm.linux.org.uk>
On 3 February 2012 10:24, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Fri, Feb 03, 2012 at 10:22:00AM +0100, javier Martin wrote:
>> Hi Russell,
>>
>> On 3 February 2012 10:10, Russell King - ARM Linux
>> <linux@arm.linux.org.uk> wrote:
>> > On Fri, Feb 03, 2012 at 09:37:48AM +0100, javier Martin wrote:
>> >> I've introduced a couple of printk() to check why this timeout is not
>> >> triggered and I've found that the value of jiffies does not increase
>> >> between loop iterations (i. e. it's like time didn't advance).
>> >>
>> >> Does anyobody know what reasons could make jiffies not being updated?
>> >
>> > Are interrupts disabled?
>>
>> Apparently not but, how could I check it for sure? Is
>> "irqs_disabled()" suitable for that purpose?
>
> Yes.
"irqs_disabled()" returns 0 in every iteration of the loop. So I guess
this means IRQs are properly enabled, but jiffies keeps being fixed.
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com
prev parent reply other threads:[~2012-02-03 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 8:37 [dmaengine] [Q] jiffies value does not increase in dma_sync_wait() javier Martin
2012-02-03 9:10 ` Russell King - ARM Linux
2012-02-03 9:22 ` javier Martin
2012-02-03 9:24 ` Russell King - ARM Linux
2012-02-03 9:43 ` javier Martin [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=CACKLOr0sDkaEFFCaby6H1h3hofxJdDbr4LXaFMebGWZ-46EwiQ@mail.gmail.com \
--to=javier.martin@vista-silicon.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).