From: Maxim Levitsky <maximlevitsky@gmail.com>
To: alsa-devel <alsa-devel@alsa-project.org>
Cc: Takashi Iwai <tiwai@suse.de>
Subject: RFC: workaround for 'azx_get_response timeout, switching to polling mode...'
Date: Thu, 04 Feb 2010 22:20:17 +0200 [thread overview]
Message-ID: <1265314817.19186.8.camel@maxim-laptop> (raw)
Hi,
Although I thought that polling mode is harmless, it sometimes isn't.
I found out that after few dozens of hibernate cycles, the timeout would
happen again kicking out first MSI, and then whole RRIB (single_cmd).
However, I also found out that if I resend the command that caused the
timeout, it would complete normally.
Even futher, it is possible to poll for this command, and send next
normally. It just works.
So interrupts do work, but sometimes (very rarely) are missed. It might
be even a hardware bug.
The patch I send allows to delay switch to polling till we get 3 such
timeouts in a row.
I tested this approach for about 130 hibernate cycles.
Best regards,
Maxim Levitsky
next reply other threads:[~2010-02-04 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 20:20 Maxim Levitsky [this message]
2010-02-04 20:21 ` [PATCH] Delay switching to polling mode if an interrupt was missing Maxim Levitsky
2010-02-05 8:13 ` RFC: workaround for 'azx_get_response timeout, switching to polling mode...' Takashi Iwai
2010-02-05 9:46 ` Maxim Levitsky
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=1265314817.19186.8.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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).