From: peter.ujfalusi@ti.com (Peter Ujfalusi)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP 4430 SDP: rather sick with recent kernels
Date: Wed, 31 Dec 2014 16:00:14 +0200 [thread overview]
Message-ID: <54A4016E.3000300@ti.com> (raw)
In-Reply-To: <20141218114949.GY11764@sirena.org.uk>
On 12/18/2014 01:49 PM, Mark Brown wrote:
> On Thu, Dec 18, 2014 at 10:16:18AM +0000, Russell King - ARM Linux wrote:
>
>> So that doesn't work - but importantly, it does point towards a
>> possible culpret - snd_soc_of_parse_audio_routing().
>
>> This is obvious when you stop and think about what it's doing, this is
>> truely where this bug lies, and it /is/ in generic ASoC code.
>
>> The problem is that this function doesn't consider the implications of
>> deferred probing. Let's see what happens if we defer, and re-do the
>> ABE initialisation, including calling this function:
>
> Right, spot on - I'll send a revert for that upstream. Thanks for
> tracking this down.
Mark, can you send the e3b1e6a19e09877b91517dfe304a2b3f6b2138fc (found it in
linux-next) for 3.19 if it not yet done? With that applied mainline boots up
on my Blaze.
--
P?ter
next prev parent reply other threads:[~2014-12-31 14:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 9:52 OMAP 4430 SDP: rather sick with recent kernels Russell King - ARM Linux
2014-12-17 17:23 ` Tony Lindgren
2014-12-17 17:33 ` Nishanth Menon
2014-12-17 17:34 ` Tony Lindgren
2014-12-17 18:51 ` Russell King - ARM Linux
2014-12-17 19:09 ` Tony Lindgren
2014-12-17 20:44 ` Tony Lindgren
2014-12-17 21:08 ` Jyri Sarha
2014-12-18 10:16 ` Russell King - ARM Linux
2014-12-18 11:48 ` Peter Rosin
2014-12-18 13:12 ` Jyri Sarha
2014-12-18 11:49 ` Mark Brown
2014-12-31 14:00 ` Peter Ujfalusi [this message]
2014-12-31 18:52 ` Mark Brown
2014-12-18 16:41 ` Tony Lindgren
2014-12-31 12:59 ` Peter Ujfalusi
2015-01-14 17:51 ` Russell King - ARM Linux
2015-01-14 19:09 ` Tony Lindgren
2015-01-14 22:27 ` Tony Lindgren
2015-01-14 23:10 ` Russell King - ARM Linux
2015-01-15 10:48 ` Russell King - ARM Linux
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=54A4016E.3000300@ti.com \
--to=peter.ujfalusi@ti.com \
--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).