From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Myunguk Kim <mwkim@gaonchips.com>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
fido_max@inbox.ru, joabreu@synopsys.com,
krzysztof.kozlowski+dt@linaro.org,
kuninori.morimoto.gx@renesas.com, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, perex@perex.cz, robh+dt@kernel.org,
tiwai@suse.com, u.kleine-koenig@pengutronix.de,
xingyu.wu@starfivetech.com
Subject: Re: [PATCH] ASoC: dwc: Add Single DMA mode support
Date: Wed, 13 Sep 2023 08:38:55 +0200 [thread overview]
Message-ID: <644e3564-994d-0b51-7d58-dac6afc1e0ec@linaro.org> (raw)
In-Reply-To: <20230913025342.1460157-1-mwkim@gaonchips.com>
On 13/09/2023 04:53, Myunguk Kim wrote:
>> Bindings are always separate patch.
>
> Okay, I will send v2.
>
>> This was not tested. Missing vendor prefix, type.
>>
>> Anyway please provide some explanation why this cannot be deduced from
>> the compatible.
>
> This is not dependent on a specific vendor,
> but is intended to describe
> the properties of the signal(single/burst request) connection
> relationship between i2s and dma.
How does this relationship depend on hardware?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-09-13 6:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 2:40 [PATCH] ASoC: dwc: Add Single DMA mode support Myunguk Kim
2023-09-11 6:12 ` Krzysztof Kozlowski
2023-09-13 2:53 ` Myunguk Kim
2023-09-13 6:38 ` Krzysztof Kozlowski [this message]
2023-09-13 6:43 ` Myunguk Kim
2023-09-13 6:58 ` Krzysztof Kozlowski
2023-09-11 12:31 ` Mark Brown
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=644e3564-994d-0b51-7d58-dac6afc1e0ec@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.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;
as well as URLs for NNTP newsgroup(s).