From: Mark Brown <broonie@kernel.org>
To: Padma Venkat <padma.kvr@gmail.com>
Cc: alsa-devel@alsa-project.org,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
Padmavathi Venna <padma.v@samsung.com>,
Sangbeom Kim <sbkim73@samsung.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
Kukjin Kim <kgene.kim@samsung.com>,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH 2/2] ASoC: samsung: Use ASoC dmaengine code where possible
Date: Wed, 27 Nov 2013 15:05:34 +0000 [thread overview]
Message-ID: <20131127150534.GW14725@sirena.org.uk> (raw)
In-Reply-To: <CAAgF-Bc5mEmOBFZak2rSuCqs+xjcrNqnVNZc=zno8F3VOCuuwA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1462 bytes --]
On Wed, Nov 27, 2013 at 06:08:47PM +0530, Padma Venkat wrote:
> On Tue, Nov 26, 2013 at 5:50 PM, Mark Brown <broonie@kernel.org> wrote:
> > So this is 16 bit stereo or something, and did it work beforehand? Like
> > I say I suspect the DMA is ending up being configured with the wrong
> > transfer size, can you check what actually happens there please - what's
> > different about the configuration that the DMA controller gets? I don't
> > have any Exynos systems with mainline audio support so I can't test
> > anything myself.
> This stream was working before. dma_size in i2s_hw_params not getting
> effected as dma_data is getting initialized only at dai probe time. So
> by default the dma_size is always 4 which is initialized at driver
> probe time. The fifo_size of dai is also always 0. It is not getting
> passed from dai driver. I just hard coded the dma_size to 2 and
But if it's initialised at probe time then when is it getting
overwritten? This must be something triggered by DT which unfortunately
I can't test. It's a bit of a shame that the flows are different
between the DT and non-DT cases.
The FIFO size looks like a difference between the pl330 and pl080, it
doesn't seem to matter for pl080. We just need to set it though.
> fifo_size to 32 then I can hear the audio only on right ear phone.
> Still underrun error message appears.
Are you sure that dma_size should be 2? The i2s DAI driver seems to be
hard coding it to 4.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-11-27 15:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 13:48 [PATCH 1/2] ASoC: samsung: Provide helper for DMA init Mark Brown
2013-11-12 13:48 ` [PATCH 2/2] ASoC: samsung: Use ASoC dmaengine code where possible Mark Brown
2013-11-26 5:25 ` [alsa-devel] " Padma Venkat
2013-11-26 10:23 ` Mark Brown
2013-11-26 10:48 ` [alsa-devel] " Padma Venkat
2013-11-26 12:20 ` Mark Brown
2013-11-27 12:38 ` Padma Venkat
2013-11-27 15:05 ` Mark Brown [this message]
2013-11-28 9:59 ` Padma Venkat
2013-11-28 11:53 ` Mark Brown
2013-12-05 10:50 ` [alsa-devel] " Padma Venkat
2013-12-05 11:45 ` Mark Brown
2013-12-09 17:52 ` Padma Venkat
2013-12-09 17:59 ` Mark Brown
2013-11-26 5:24 ` [alsa-devel] [PATCH 1/2] ASoC: samsung: Provide helper for DMA init Padma Venkat
2013-11-26 10:15 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2013-12-05 14:25 Mark Brown
2013-12-05 14:25 ` [PATCH 2/2] ASoC: samsung: Use ASoC dmaengine code where possible Mark Brown
2013-12-06 5:14 ` [alsa-devel] " Padma Venkat
2013-12-09 17:30 ` Mark Brown
2013-12-10 16:39 ` Padma Venkat
2013-12-10 17:01 ` Mark Brown
2013-12-06 12:57 [PATCH 1/2] ASoC: samsung: Provide helper for DMA init Mark Brown
2013-12-06 12:57 ` [PATCH 2/2] ASoC: samsung: Use ASoC dmaengine code where possible Mark Brown
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=20131127150534.GW14725@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=kgene.kim@samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=padma.kvr@gmail.com \
--cc=padma.v@samsung.com \
--cc=sbkim73@samsung.com \
--cc=tomasz.figa@gmail.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