[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120124114210.GB14888@opensource.wolfsonmicro.com>
Date: Tue, 24 Jan 2012 11:42:10 +0000
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Tomoya MORINAGA <tomoya.rohm@...il.com>
Cc: Liam Girdwood <lrg@...com>, Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.de>,
Lars-Peter Clausen <lars@...afoo.de>,
Dimitris Papastamos <dp@...nsource.wolfsonmicro.com>,
Mike Frysinger <vapier@...too.org>,
Daniel Mack <zonque@...il.com>, alsa-devel@...a-project.org,
linux-kernel@...r.kernel.org
Subject: Re: Hang up at .prepare( )
On Tue, Jan 24, 2012 at 08:30:17PM +0900, Tomoya MORINAGA wrote:
> 2012/1/24 Mark Brown <broonie@...nsource.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists