From: Mark Brown <broonie@kernel.org>
To: Shengjiu Wang <shengjiu.wang@nxp.com>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
timur@kernel.org, Xiubo.Lee@gmail.com, lgirdwood@gmail.com,
linuxppc-dev@lists.ozlabs.org, tiwai@suse.com, perex@perex.cz,
nicoleotsuka@gmail.com, robh+dt@kernel.org, festevam@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] ASoC: fsl_esai: Add support for imx8qm
Date: Fri, 1 May 2020 11:21:58 +0100 [thread overview]
Message-ID: <20200501102158.GA5276@sirena.org.uk> (raw)
In-Reply-To: <a933bafd2d6a60a69f840d9d4b613337efcf2816.1588320656.git.shengjiu.wang@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]
On Fri, May 01, 2020 at 04:12:05PM +0800, Shengjiu Wang wrote:
> The difference for esai on imx8qm is that DMA device is EDMA.
>
> EDMA requires the period size to be multiple of maxburst. Otherwise
> the remaining bytes are not transferred and thus noise is produced.
If this constraint comes from the DMA controller then normally you'd
expect the DMA controller integration to be enforcing this - is there no
information in the DMA API that lets us know that this constraint is
there?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-05-01 10:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 8:12 [PATCH 0/3] ASoC: fsl_esai: Add support for imx8qm Shengjiu Wang
2020-05-01 8:12 ` [PATCH 1/3] ASoC: fsl_esai: introduce SoC specific data Shengjiu Wang
2020-05-04 21:39 ` Nicolin Chen
2020-05-01 8:12 ` [PATCH 2/3] ASoC: fsl_esai: Add support for imx8qm Shengjiu Wang
2020-05-01 10:21 ` Mark Brown [this message]
2020-05-06 2:33 ` Shengjiu Wang
2020-05-12 2:48 ` Shengjiu Wang
2020-05-12 12:38 ` Mark Brown
2020-05-15 10:01 ` Shengjiu Wang
2020-05-01 8:12 ` [PATCH 3/3] ASoC: fsl_esai: Add new compatible string " Shengjiu Wang
2020-05-12 16:38 ` Rob Herring
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=20200501102158.GA5276@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nicoleotsuka@gmail.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=shengjiu.wang@nxp.com \
--cc=timur@kernel.org \
--cc=tiwai@suse.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).