From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tomoya MORINAGA <tomoya.rohm@gmail.com>
Cc: Liam Girdwood <lrg@ti.com>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
Mike Frysinger <vapier@gentoo.org>,
Daniel Mack <zonque@gmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: Hang up at .prepare( )
Date: Tue, 24 Jan 2012 11:42:10 +0000 [thread overview]
Message-ID: <20120124114210.GB14888@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CANKRQnibHChSVEOvsDuKTXcnDkx5KQAMOxfheocTJt+ar0CgPw@mail.gmail.com>
On Tue, Jan 24, 2012 at 08:30:17PM +0900, Tomoya MORINAGA wrote:
> 2012/1/24 Mark Brown <broonie@opensource.wolfsonmicro.com>:
> > What efforts have you made to debug this yourself? Clearly this is not
> > happening for other people, perhaps it is related to something you have
> > in your drivers - have you addressed the issues raised with them?
> I said previously, "our ASoC drivers" not others.
> Of course, I understand current upstreamed drivers don't have this issue.
> I just asked "If someone faced the same issue when debugging, let me
> know about it."
That's not answering my question - I'm asking you what steps you've
taken to progress, to explain the analysis you've done so far. For
example, what is the blocked thread blocked on - what is it waiting for
and why has that thing happened?
If you have not addressed the review issues with your driver then take a
look at those, perhaps the problem has already been identified through
code review.
prev parent reply other threads:[~2012-01-24 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 9:38 Hang up at .prepare( ) Tomoya MORINAGA
2012-01-24 10:55 ` Mark Brown
2012-01-24 11:30 ` Tomoya MORINAGA
2012-01-24 11:42 ` Mark Brown [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=20120124114210.GB14888@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dp@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
--cc=tomoya.rohm@gmail.com \
--cc=vapier@gentoo.org \
--cc=zonque@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox