From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Daniel Drake <drake@endlessm.com>
Cc: devicetree@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
pawel.moll@arm.com, zhen1.chen@samsung.com,
Kyungmin Park <kyungmin.park@samsung.com>,
galak@codeaurora.org, alsa-devel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH V2 0/2] Sound support for Exynos4412 Odroid X2, U3 board
Date: Mon, 23 Jun 2014 18:32:46 +0200 [thread overview]
Message-ID: <53A856AE.1030202@samsung.com> (raw)
In-Reply-To: <CAD8Lp44h6zc2Rt2MGLjhmNG-YB0kYCWf5G7hX5JmdmBfc1PvKg@mail.gmail.com>
On 23/06/14 11:40, Daniel Drake wrote:
> I tested ODROID-U2's 3.5mm analog headphone jack output with:
>
> # speaker-test -c 2 -t wav -l 2
>
> On my x86 laptop this command takes ~6 seconds and produces audible output:
> "Front left, front right, front left, front right"
>
> When those words are reproduced over the speakers, there is a
> corresponding message printed to stdout which synchronizes nicely.
>
> On ODROID-U2 the same command doesn't work quite right - execution
> takes only 3.5 seconds and the audible output is truncated:
> "Front left, front right, front"
> and the stdout messages do not really coincide with the audio being
> reproduced at that time.
>
> No pulseaudio or anything like that.
>
> Can you reproduce this?
I could reproduce such behaviour on the U3 board, but only with u-boot
which sets the MPLL clock frequency (fout_mpll) to 880 MHz, rather
than 800 MHz, which was the case in my original environment.
All fout_mpll child clocks have then different frequency values
in both cases.
It's a bit strange though, because frequencies of all the audio
subsystem clocks seem to be same anyway:
# cat /sys/kernel/debug/clk/clk_summary
...
fout_epll 0 0 192000000
mout_audss 0 0 192000000
dout_rp 0 0 19200000
dout_aud_bus 0 0 19200000
mout_i2s0 0 0 192000000
dout_i2s0 0 0 192000000
sclk_epll 0 0 192000000
audss 0 0 192000000
So there might be some other difference I'm overlooking.
Will let you know as soon I find out anything else.
Regards,
Sylwester
next prev parent reply other threads:[~2014-06-23 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 16:22 [PATCH V2 0/2] Sound support for Exynos4412 Odroid X2, U3 board Sylwester Nawrocki
2014-06-18 16:22 ` [PATCH V2 1/2] ASoC: samsung: Add machine driver for Odroid X2/U3 Sylwester Nawrocki
2014-06-30 18:46 ` Mark Brown
2014-07-14 11:27 ` Sylwester Nawrocki
2014-07-14 11:31 ` Mark Brown
2014-06-18 16:22 ` [PATCH V2 2/2] doc: dt bindings: Document Odroid X2/U3 audio subsystem bindings Sylwester Nawrocki
2014-06-23 9:40 ` [PATCH V2 0/2] Sound support for Exynos4412 Odroid X2, U3 board Daniel Drake
2014-06-23 16:32 ` Sylwester Nawrocki [this message]
[not found] ` <53A856AE.1030202-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-06-23 16:53 ` Sylwester Nawrocki
2014-06-24 8:35 ` Daniel Drake
2014-06-24 9:02 ` Marek Szyprowski
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=53A856AE.1030202@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=alsa-devel@vger.kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=drake@endlessm.com \
--cc=galak@codeaurora.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=zhen1.chen@samsung.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