From: Jarkko Nikula <jhnikula@gmail.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 0/2] ASoC: tlv320dac33 fixes
Date: Thu, 11 Mar 2010 17:07:38 +0200 [thread overview]
Message-ID: <20100311170738.a91bff10.jhnikula@gmail.com> (raw)
In-Reply-To: <201003111655.12504.peter.ujfalusi@nokia.com>
On Thu, 11 Mar 2010 16:55:12 +0200
Peter Ujfalusi <peter.ujfalusi@nokia.com> wrote:
> > Just curious: what would happen if the BCLK is cut while the McBSP is
> > operating?
>
> The symptom is that we can not access to McBSP register address space causing
> kernel panic, which can only be fixed by rebooting the device.
> The burst driven BCLK causes some internal state machine to stuck, leaving the
> given McBSP port dead from the outside. Other ports operate after this event.
> Obviously this only bites in McBSP slave mode, and with codec like DAC33 which
> have burst mode, in other cases the BCLK is always running (or McBSP is master).
>
> > I'm thinking are there also other similar problems, e.g. if
> > the rate is not correct.
>
> Hmmm, could be possible, but I did not experienced with such a problem.
>
Thanks for sharing this info.
Sounds exactly similar problem what I encountered once with the OMAP2420
and EAC. I didn't debug that problem any further then but there also
some register accesses (not all) caused kernel panic if the external
clock was missing or if the rate wasn't correct.
--
Jarkko
next prev parent reply other threads:[~2010-03-11 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 14:26 [PATCH 0/2] ASoC: tlv320dac33 fixes Peter Ujfalusi
2010-03-11 14:26 ` [PATCH 1/2] ASoC: tlv320dac33: Start/stop sequence change Peter Ujfalusi
2010-03-12 8:10 ` Liam Girdwood
2010-03-11 14:26 ` [PATCH 2/2] ASoC: tlv320dac33: Add option for keeping the BCLK running Peter Ujfalusi
2010-03-12 8:10 ` Liam Girdwood
2010-03-11 14:46 ` [PATCH 0/2] ASoC: tlv320dac33 fixes Jarkko Nikula
2010-03-11 14:55 ` Peter Ujfalusi
2010-03-11 15:07 ` Jarkko Nikula [this message]
2010-03-12 11:18 ` 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=20100311170738.a91bff10.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
--cc=peter.ujfalusi@nokia.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;
as well as URLs for NNTP newsgroup(s).