From: Mark Brown <broonie@kernel.org>
To: John Graham <johngavingraham@googlemail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA SOC Driver (mxs-wm8753)
Date: Mon, 29 Apr 2013 21:41:41 +0100 [thread overview]
Message-ID: <20130429204141.GI3270@sirena.org.uk> (raw)
In-Reply-To: <CAFio4Nem+9fj+=iUxN1awP=ZBzh=1Eca1kPi1ShjjjLR_9eO6A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 955 bytes --]
On Mon, Mar 04, 2013 at 06:25:05PM +0000, John Graham wrote:
You should CC maintainers on e-mails, often things just on the list get
lost in the noise.
> The problem now is that the I2S data lines don't look right - the line
> from codec to TX28 looks like a (more-or-less) square wave with the
> same period as the I2S clock, but only going from ~3.1 - ~3.5 V, as
> opposed to the 0 - ~3.3 V I expect. Furthermore, it's a pretty regular
> square wave - it doesn't have all the breaks you see on a working I2S
> data line.
My immediate thought here is that you're probably seeing some sort of
electrical problem if the logic levels aren't being hit - normally this
is because both ends of the link are driving simultaneously. I'd check
the pin mux settings on the SoC, probably in arch/arm, to make sure that
everything on the SoC is in the correct mode then check that the CPU is
configured as a slave (which sounds like the intended configuration).
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-04-29 20:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 18:25 ALSA SOC Driver (mxs-wm8753) John Graham
2013-04-29 20:41 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-15 9:14 Kevin Startup
2014-07-18 8:44 ` Charles Keepax
2014-07-18 10:14 ` Kevin Startup
2014-07-18 10:53 ` Charles Keepax
2014-07-18 13:02 ` Kevin Startup
2014-07-18 14:28 ` Charles Keepax
2014-07-23 8:40 ` Kevin Startup
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=20130429204141.GI3270@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=johngavingraham@googlemail.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