From: Mark Brown <broonie@kernel.org>
To: Myunguk Kim <mwkim@gaonchips.com>
Cc: alsa-devel@alsa-project.org, "Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Maxim Kochetkov" <fido_max@inbox.ru>,
"Xingyu Wu" <xingyu.wu@starfivetech.com>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"Uw e Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-kernel@vger.kernel.org, "Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Jose Abreu" <joabreu@synopsys.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] ASoC: dwc: Add Single DMA mode support
Date: Mon, 11 Sep 2023 13:31:41 +0100 [thread overview]
Message-ID: <ZP8Irf6g+sG6Ax9j@finisterre.sirena.org.uk> (raw)
In-Reply-To: <20230911024023.43833-1-mwkim@gaonchips.com>
[-- Attachment #1: Type: text/plain, Size: 619 bytes --]
On Mon, Sep 11, 2023 at 11:40:23AM +0900, Myunguk Kim wrote:
> There is a SoC between dwc and DMA block (ie. PL330)
> that does not have a burst signal and supports only single.
>
> So write not-support-burst property on dts, it support single DMA mode.
This feels like something we ought to be discovering from the DMA API
somehow, while it's not quite a property of the DMA controller (but
rather of the SoC integration) in this case it could be a property of
some DMA controller elsewhere and the whole process of finding and
figuring out the properties of the DMA controler is handled by the DMA
API.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-09-11 20:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 2:40 Myunguk Kim
2023-09-11 6:12 ` Krzysztof Kozlowski
2023-09-13 2:53 ` Myunguk Kim
2023-09-13 6:38 ` Krzysztof Kozlowski
2023-09-13 6:43 ` Myunguk Kim
2023-09-13 6:58 ` Krzysztof Kozlowski
2023-09-11 12:31 ` Mark Brown [this message]
2023-09-13 4:09 ` Myunguk Kim
2023-09-13 15:07 ` 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=ZP8Irf6g+sG6Ax9j@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fido_max@inbox.ru \
--cc=joabreu@synopsys.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mwkim@gaonchips.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=xingyu.wu@starfivetech.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
all inboxes | Powered by JetHome®