From: Timur Tabi <timur@freescale.com>
To: avorontsov@ru.mvista.com
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] [ALSA] soc - fsl_ssi.c fix "BUG: scheduling while atomic"
Date: Thu, 08 May 2008 14:43:51 -0500 [thread overview]
Message-ID: <482357F7.60602@freescale.com> (raw)
In-Reply-To: <20080508194146.GA5816@polina.dev.rtsoft.ru>
Anton Vorontsov wrote:
> Are there any drawbacks of mdelay'ing?
All I remember is that without the delay, it wouldn't work. But that was a long
time ago, and I never revisited the issue, even after the silicon was updated.
> Since some silicons need this
> we'd better leave it then.
The 1.0 silicon is dead and won't work with this driver anyway. We should still
leave it in for now, but I plan on doing thorough testing without it. If the
driver still works, I'll remove it for ASoC V2.
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2008-05-08 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 16:01 [PATCH] [ALSA] soc - fsl_ssi.c fix "BUG: scheduling while atomic" Anton Vorontsov
2008-05-08 19:19 ` Timur Tabi
2008-05-08 19:41 ` Anton Vorontsov
2008-05-08 19:43 ` Timur Tabi [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=482357F7.60602@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=avorontsov@ru.mvista.com \
--cc=broonie@opensource.wolfsonmicro.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.