From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: "Ujfalusi, Peter" <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: Thu, 21 Jun 2012 19:58:15 +0100 [thread overview]
Message-ID: <20120621185815.GA2426@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAPo=G1wbwt_wO8HV7+WqTqDcFO6bbjj2eYSNwNVMGyhDM_1vuw@mail.gmail.com>
On Thu, Jun 21, 2012 at 09:36:12PM +0300, Ujfalusi, Peter wrote:
> Hi Russel,
>
> On Thu, Jun 21, 2012 at 4:22 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> >> Okay, reverting back to v3.4-rc4 works.
> >
> > As does reverting to v3.4, of course. So, it was broken during the last
> > merge window.
>
> Strange...
> I had no problem with the SDP4430/Blaze audio with 3.5-rc2 last week.
> Have you restored the mixers with
> alsactl -f blaze.aconf restore
> command?
>
> Does aplay (seemingly) plays the file OK or is it times out with an
> error after a while?
It is as I said:
v3.5-rc3:
# alsactl -f blaze.aconf restore
# aplay -f S16_LE -r 48000 -c 2 file.raw
... plays in about the right time but no audio ...
v3.5-rc3 with the diff from v3.4..v3.5-rc5 for sound/soc/omap totally
reverted:
# alsactl -f blaze.aconf restore
# aplay -f S16_LE -r 48000 -c 2 file.raw
... plays perfectly ...
Exactly the same procedure. Only difference is I've backed out _all_ the
updates to sound/soc/omap. Clearly something in there is buggered.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-06-21 18:58 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
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 [this message]
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=20120621185815.GA2426@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