From: Dave Young <dyoung@redhat.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Jarkko Nikula <jarkko.nikula@bitmer.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org
Subject: Re: omap-mcbsp 49022000.mcbsp: TX Buffer Overflow!
Date: Tue, 21 Jul 2020 11:18:36 +0800 [thread overview]
Message-ID: <20200721031836.GC5271@dhcp-128-65.nay.redhat.com> (raw)
In-Reply-To: <d8829b8a-eca7-f0e3-600f-3263619332b3@ti.com>
Hi Peter
On 07/20/20 at 12:32pm, Peter Ujfalusi wrote:
> Hi,
>
> On 20/07/2020 12.03, Peter Ujfalusi wrote:
> > Hi,
> >
> > On 14/07/2020 21.03, Jarkko Nikula wrote:
> >> Hi
> >>
> >> On 7/11/20 6:33 AM, Dave Young wrote:
> >>> Hi,
> >>>
> >>> I'm trying to use g_audio on my Nokia N900 with mainline kernel. Seems
> >>> it does not work. No sound when I play from a laptop, and also see a
> >>> lot of error like below:
> >>> [ 4729.557647] omap-mcbsp 49022000.mcbsp: TX Buffer Overflow!
> >>> ...
> >>>
> >> Head 0dc589da873b ("Merge tag 'iommu-fixes-v5.8-rc5' of
> >> git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu") records and
> >> plays fine here (arecord -f dat |aplay), although I see some of those
> >> errors but don't hear any glitches etc.
> >>
> >> Peter, does above indicate a serious issue or is it perhaps a false
> >> alarm on OMAP3 (no audible glitches)?
> >
> > I need to dig out my n900 or beagleXM, but it is hard to believe it is
> > not a result of a glitch.
> > The DMA is triggered by McBSP and it should write exactly what McBSP
> > expects to be receiving.
> >
> > I can not recall any changes in the past years which would have
> > introduced regressions in McBSP or the sDMA driver.
>
> I have booted linux-next on my BeagleXM (OMAP3630, McBSP2 <-> twl4030)
> and I don't see the TX overflow print.
Just to clarify, the sound works well on n900 for normal use cases.
The TX overflow only happens when I use it as an usb audio gadget.
Because n900 is old, I tried to use it as an external audio device.
>
> I have checked element and threshold modes and it looks fine.
> I'm not sure why we have TX Overflow printed on n900.
>
> >> I believe you don't have some mixer knob on, N900 audio path is somewhat
> >> complex and needs bunch of mixer switches and volumes to be set. I
> >> attached my N900 mixer scripts for you to try.
> >
> > This could be the reason for the silence, I have asoundrc files
> > somewhere to restore a 'good' mixer config.
> >
> >> Set first everything off:
> >> ./aic34_scripts/shutdown.sh
> >>
> >> Then enable internal digital microphone and speakers:
> >> ./aic34_scripts/dmic.sh
> >> ./aic34_scripts/speakers.sh
> >>
> >> Hopefully these help you get going :-)
> >>
> >
> > - Péter
> >
> > Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
> > Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
> >
>
> - Péter
>
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
> Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
>
Thanks
Dave
prev parent reply other threads:[~2020-07-21 3:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 3:33 omap-mcbsp 49022000.mcbsp: TX Buffer Overflow! Dave Young
2020-07-14 18:03 ` Jarkko Nikula
2020-07-20 9:03 ` Peter Ujfalusi
2020-07-20 9:32 ` Peter Ujfalusi
2020-07-21 3:18 ` Dave Young [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=20200721031836.GC5271@dhcp-128-65.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=alsa-devel@alsa-project.org \
--cc=jarkko.nikula@bitmer.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@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;
as well as URLs for NNTP newsgroup(s).