From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Rick Mann <rmann@latencyzero.com>
Cc: Alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: mcasp: stream has more channels (2) than are enabled in mcasp (0)
Date: Tue, 19 Apr 2016 10:00:05 +0300 [thread overview]
Message-ID: <5715D775.8030303@ti.com> (raw)
In-Reply-To: <5D6815AB-B3DF-4F4F-BC0D-33612A202975@latencyzero.com>
On 04/19/16 03:25, Rick Mann wrote:
> Thanks for the suggestions, Peter, I really appreciate the help. Here's
> what I get:
>
> [ 256.743991] davinci-mcasp 48038000.mcasp: Slots: 2,
> max_active_serializers: 1, active_serializers: 0, channels: 2
>
> I rebuilt the 4.4.7-bone-rt-r9 kernel using Robert C Nelson's bb-kernel
> repo scripts. I modified sound/soc/davinci/davinci-mcasp.c to print some
> diagnostics. Rebooted, then executed the following. Note that
> BB-BONE-AUDI-02.dts is
> <https://github.com/RobertCNelson/bb.org-overlays/blob/master/src/arm/BB-BONE-AUDI-02-00A0.dts>,
> and the base DTB is <http://pastebin.com/5vVEdAKt>:
Looks OK.
FWIW: I have the following patch on top of linux-next to get the BBW's
AudioCape RevA working:
https://github.com/omap-audio/linux-audio/commit/37d2421c321762360a6982b37107b617b0f74bee
> $ sudo su # echo BB-BONE-AUDI-02 > $SLOTS # aplay -l **** List of PLAYBACK
> Hardware Devices **** card 0: B [AudioCape Rev B], device 0:
> davinci-mcasp.0-tlv320aic3x-hifi tlv320aic3x-hifi-0 [] Subdevices: 1/1
> Subdevice #0: subdevice #0 # speaker-test
>
> speaker-test 1.0.28
>
> Playback device is default Stream parameters are 48000Hz, S16_LE, 1
> channels Using 16 octaves of pink noise Rate set to 48000Hz (requested
> 48000Hz) Buffer size range from 16 to 32768 Period size range from 8 to
> 16384 Using max buffer size 32768 Periods = 4 Unable to set hw params for
> playback: Invalid argument Setting of hwparams failed: Invalid argument
>
> speaker-test caused the following to be logged:
>
> [ 256.743991] davinci-mcasp 48038000.mcasp: Slots: 2,
> max_active_serializers: 1, active_serializers: 0, channels: 2
Now this is odd... Can you print also the mcasp->num_serializer here? If it is
0, then something really strange is going on.
We set this up in davinci_mcasp_set_pdata_from_of() when reading the
serial-dir array.
> [256.754343] davinci-mcasp 48038000.mcasp: ASoC: can't set 48038000.mcasp hw
> params: -22
>
>
> Full logs:
>
> http://pastebin.com/HGhu9CPk
>
>
>
>
--
Péter
next prev parent reply other threads:[~2016-04-19 7:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 8:59 mcasp: stream has more channels (2) than are enabled in mcasp (0) Rick Mann
2016-04-18 15:36 ` Peter Ujfalusi
2016-04-19 0:25 ` Rick Mann
2016-04-19 0:48 ` Rick Mann
2016-04-19 7:00 ` Peter Ujfalusi [this message]
2016-04-19 7:18 ` Rick Mann
2016-04-19 7:36 ` Peter Ujfalusi
2016-04-19 8:05 ` Rick Mann
2016-04-19 8:37 ` Peter Ujfalusi
2016-04-19 9:04 ` Rick Mann
2016-04-19 9:22 ` Peter Ujfalusi
2016-04-19 9:32 ` Rick Mann
2016-04-19 11:17 ` Peter Ujfalusi
2016-06-03 13:22 ` ASoC: TLV320AIC3x changing suspend delay time Timur Karaldin
2016-06-03 14:38 ` Timur Karaldin
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=5715D775.8030303@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=rmann@latencyzero.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).