From: Christoph Fritz <chf.fritz@googlemail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: alsa-devel@alsa-project.org,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Mark Brown" <broonie@opensource.wolfsonmicro.com>,
"Sascha Hauer" <kernel@pengutronix.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Shawn Guo" <shawn.guo@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: Lockups reading from i.MX51 SSI registers
Date: Sat, 18 Aug 2012 08:31:28 +0200 [thread overview]
Message-ID: <1345271488.3694.1.camel@lovely> (raw)
In-Reply-To: <CAOMZO5BgeW_z-zf3Auw6RCJg1o5L=DqWdVeF+0Xb_W=6hZJMnQ@mail.gmail.com>
On Fri, 2012-08-17 at 20:35 -0300, Fabio Estevam wrote:
> On Fri, Aug 17, 2012 at 7:27 PM, Mark Brown
> <broonie@opensource.wolfsonmicro.com> wrote:
> > On Fri, Aug 17, 2012 at 04:08:47PM -0300, Fabio Estevam wrote:
> >
> >> Also, for the playback to work you need to install the SDMA firmware.
> >
> > This is deadlocking during boot, I'm getting nowhere near trying
> > playback.
>
> Are you running a dt or non-dt kernel? In case of a dt kernel, can you
> share the dts file?
I suppose Mark means an i.MX35 not an i.MX51.
WARNING: multiple messages have this Message-ID (diff)
From: chf.fritz@googlemail.com (Christoph Fritz)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] Lockups reading from i.MX51 SSI registers
Date: Sat, 18 Aug 2012 08:31:28 +0200 [thread overview]
Message-ID: <1345271488.3694.1.camel@lovely> (raw)
In-Reply-To: <CAOMZO5BgeW_z-zf3Auw6RCJg1o5L=DqWdVeF+0Xb_W=6hZJMnQ@mail.gmail.com>
On Fri, 2012-08-17 at 20:35 -0300, Fabio Estevam wrote:
> On Fri, Aug 17, 2012 at 7:27 PM, Mark Brown
> <broonie@opensource.wolfsonmicro.com> wrote:
> > On Fri, Aug 17, 2012 at 04:08:47PM -0300, Fabio Estevam wrote:
> >
> >> Also, for the playback to work you need to install the SDMA firmware.
> >
> > This is deadlocking during boot, I'm getting nowhere near trying
> > playback.
>
> Are you running a dt or non-dt kernel? In case of a dt kernel, can you
> share the dts file?
I suppose Mark means an i.MX35 not an i.MX51.
next prev parent reply other threads:[~2012-08-18 6:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 19:50 Lockups reading from i.MX51 SSI registers Mark Brown
2012-08-10 19:50 ` Mark Brown
2012-08-10 19:56 ` Sascha Hauer
2012-08-10 19:56 ` Sascha Hauer
2012-08-10 20:14 ` Uwe Kleine-König
2012-08-10 20:14 ` Uwe Kleine-König
2012-08-10 21:06 ` Sascha Hauer
2012-08-10 21:06 ` Sascha Hauer
2012-08-17 19:08 ` Fabio Estevam
2012-08-17 19:08 ` [alsa-devel] " Fabio Estevam
2012-08-17 22:27 ` Mark Brown
2012-08-17 22:27 ` [alsa-devel] " Mark Brown
2012-08-17 23:35 ` Fabio Estevam
2012-08-17 23:35 ` [alsa-devel] " Fabio Estevam
2012-08-18 6:31 ` Christoph Fritz [this message]
2012-08-18 6:31 ` Christoph Fritz
2012-08-20 13:18 ` Mark Brown
2012-08-20 13:18 ` [alsa-devel] " Mark Brown
2012-08-20 13:24 ` Fabio Estevam
2012-08-20 13:24 ` [alsa-devel] " Fabio Estevam
2012-08-18 7:42 ` Uwe Kleine-König
2012-08-18 7:42 ` [alsa-devel] " Uwe Kleine-König
2012-08-18 14:53 ` Fabio Estevam
2012-08-18 14:53 ` [alsa-devel] " Fabio Estevam
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=1345271488.3694.1.camel@lovely \
--to=chf.fritz@googlemail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=u.kleine-koenig@pengutronix.de \
/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.