From: Lee Jones <lee.jones@linaro.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: "Philippe Rétornaz" <philippe.retornaz@epfl.ch>,
alsa-devel@alsa-project.org,
"Mark Brown" <broonie@opensource.wolfsonmicro.com>,
"Sascha Hauer" <kernel@pengutronix.de>
Subject: Re: Crash when probing imx_mc13783
Date: Thu, 26 Jul 2012 17:15:52 +0100 [thread overview]
Message-ID: <50116D38.6050001@linaro.org> (raw)
In-Reply-To: <CAOMZO5BsOV3X09DKc-uexe9mqhYhkbmKZg2vh_h2-hBB=X1A7Q@mail.gmail.com>
On 26/07/12 16:40, Fabio Estevam wrote:
> Philippe,
>
> On Thu, Jul 26, 2012 at 4:29 AM, Philippe Rétornaz
> <philippe.retornaz@epfl.ch> wrote:
>
>> Well, I'm able to boot 3.5 on my board (imx31 based), so it must be a patch
>> between 3.5 and 3.5-next. It should be quite quickly bisectable.
>
> It turns out I am having the same issue as the one described at:
> https://lkml.org/lkml/2012/7/26/128
>
> I applied Lee's patch and audio can be probed again. I am not sure how
> would be the right fix in our case though.
The patch is apparently not correct (although, I do see a place for it).
The problem is that unless your code populates codec->control_data, SoC
Core will assume you haven't set-up any I/O for yourself, even if you
have. I'm just chatting with Mark now to try to get to the bottom of
what I need to put in there for my use-case. I'm assuming yours will be
different again.
Kind regards,
Lee
--
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2012-07-26 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 19:56 Crash when probing imx_mc13783 Fabio Estevam
2012-07-26 7:29 ` Philippe Rétornaz
2012-07-26 15:40 ` Fabio Estevam
2012-07-26 16:15 ` Lee Jones [this message]
2012-07-26 17:16 ` Fabio Estevam
2012-07-26 20:20 ` Mark Brown
2012-07-26 20:19 ` Mark Brown
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=50116D38.6050001@linaro.org \
--to=lee.jones@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=philippe.retornaz@epfl.ch \
/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.