From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: imx sgtl5000:BUG: scheduling while atomic: speaker-test/1225/0x00000003
Date: Thu, 26 Apr 2012 10:11:31 +0200 [thread overview]
Message-ID: <20120426081131.GZ20478@pengutronix.de> (raw)
In-Reply-To: <20377.289.954415.840587@ipc1.ka-ro>
On Thu, Apr 26, 2012 at 10:02:41AM +0200, Lothar Wa?mann wrote:
> Hi,
>
> Sascha Hauer writes:
> > On Thu, Apr 26, 2012 at 09:29:17AM +0200, Lothar Wa?mann wrote:
> > > Hi,
> > >
> > > > > - init_completion(&sdmac->done);
> > > > > + unsigned long timeout = 500;
> > > > I'm not sure. Did you test 500us is enough for loading firmware?
> > > >
> > > Channel 0 is not used for actual data transfer but for some internal
> > > housekeeping. Thus the timeout is independent from the time required
> > > for the actual data transfer.
> > > I haven't seen any timeout even with the timeout set to 100us.
> > > Usually it takes 3 to 4 us to complete.
> >
> > It *is* used to load the firmware. Have you tested your patch with
> > actually loading a firmware?
> >
> I'm using it around 100 times a day (with a 100us timeout)...
That should be enough ;)
I am fine with the patch.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2012-04-26 8:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 2:33 imx sgtl5000:BUG: scheduling while atomic: speaker-test/1225/0x00000003 Richard Zhao
2012-04-26 3:00 ` Fabio Estevam
2012-04-26 3:04 ` Richard Zhao
2012-04-26 5:12 ` Richard Zhao
2012-04-26 6:10 ` Lothar Waßmann
2012-04-26 6:44 ` Richard Zhao
2012-04-26 7:29 ` Lothar Waßmann
2012-04-26 7:36 ` Sascha Hauer
2012-04-26 8:02 ` Lothar Waßmann
2012-04-26 8:11 ` Sascha Hauer [this message]
2012-04-26 8:16 ` Richard Zhao
2012-04-26 9:13 ` Richard Zhao
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=20120426081131.GZ20478@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).