From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: linux-omap@vger.kernel.org,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: Audio support on OMAP 3430LDP or 4430SDP boards
Date: Tue, 1 May 2012 12:14:00 +0100 [thread overview]
Message-ID: <20120501111400.GF25053@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4F9E3EB5.8030104@ti.com>
On Mon, Apr 30, 2012 at 10:26:45AM +0300, Peter Ujfalusi wrote:
> On 04/29/2012 11:35 PM, Russell King - ARM Linux wrote:
> > Please can someone at TI take a current mainline kernel, build it, and
> > test out audio support on the 4430SDP - specifically output through the
> > headset jack into a line input, and report when it works. Thanks.
>
> Try to use my attached aconf for SDP4430 to configure the HS playback.
> Note that the HS is not a line out, so on your line-in device it will
> cause distortion. If you have a headset/headphone you will have better
> quality.
> alsactl -f blaze.aconf restore
This had no effect on its own.
> To play samples with aplay:
> aplay -Dplughw:0,0 <wav file>
> The sample format fot Legacy McPDM is S32_LE, 96KHz, 24bit (32 bit
> sample with 24 LSB).
>
> The slow pace audio playback is because at this point we do not have the
> full audio stack up. The AESS IP does not have driver. You need to
> disable CONFIG_OMAP_RESET_CLOCKS. This will fic the audio playback speed.
But with that configuration file and that option disabled, I now get
audio output via the HS jack. Bellowhead sounds a lot better now.
next prev parent reply other threads:[~2012-05-01 11:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 13:58 Audio support on OMAP 3430LDP or 4430SDP boards Russell King - ARM Linux
2012-04-27 14:15 ` Shilimkar, Santosh
2012-04-27 14:56 ` Liam Girdwood
2012-04-27 15:09 ` Russell King - ARM Linux
2012-04-27 15:53 ` Ujfalusi, Peter
2012-04-27 16:04 ` Russell King - ARM Linux
2012-04-27 16:32 ` Ujfalusi, Peter
2012-04-27 16:50 ` Russell King - ARM Linux
2012-04-27 17:04 ` Ujfalusi, Peter
2012-04-27 17:19 ` Russell King - ARM Linux
2012-04-27 18:14 ` Ujfalusi, Peter
2012-04-27 18:31 ` Russell King - ARM Linux
2012-04-27 19:17 ` Ujfalusi, Peter
2012-04-27 19:31 ` Russell King - ARM Linux
2012-04-29 20:35 ` Russell King - ARM Linux
2012-04-30 7:26 ` Peter Ujfalusi
2012-05-01 11:14 ` Russell King - ARM Linux [this message]
2012-06-21 12:59 ` Russell King - ARM Linux
2012-06-21 13:16 ` Russell King - ARM Linux
2012-06-21 13:22 ` Russell King - ARM Linux
2012-06-21 18:36 ` Ujfalusi, Peter
2012-06-21 18:58 ` Russell King - ARM Linux
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=20120501111400.GF25053@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=santosh.shilimkar@ti.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