From: <Claudiu.Beznea@microchip.com>
To: <broonie@kernel.org>, <lars@metafoo.de>
Cc: devicetree@vger.kernel.org, alexandre.belloni@bootlin.com,
alsa-devel@alsa-project.org, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, tiwai@suse.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, perex@perex.cz,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] ASoC: soc-generic-dmaengine-pcm: add option to start DMA after DAI
Date: Thu, 16 Feb 2023 09:49:49 +0000 [thread overview]
Message-ID: <4b109846-2019-219a-262e-46f5bb504c99@microchip.com> (raw)
In-Reply-To: <Y+v8bbr4cNSOA1SF@sirena.org.uk>
On 14.02.2023 23:26, Mark Brown wrote:
> On Tue, Feb 14, 2023 at 10:14:28AM -0800, Lars-Peter Clausen wrote:
>> On 2/14/23 08:14, Claudiu Beznea wrote:
>>> @@ -450,6 +450,8 @@ int snd_dmaengine_pcm_register(struct device *dev,
>>> else
>>> driver = &dmaengine_pcm_component;
>>> + driver->start_dma_last = config->start_dma_last;
>> This will break if you have multiple sound cards in the system.
>> dmaengine_pcm_component must stay const.
> Right, if we need to modify it we either need to select which of
> multiple const structs to register or to take a copy and modify
> that. I've not looked at the actual changes yet.
OK, I will try that and return with a new patch.
On the other hand do you think the other solution presented in cover letter
would be better? From the cover letter:
"The other solution that was identified for this was to extend the already
existing mechanism around struct snd_soc_dai_link::stop_dma_first. The downside
of this was that a potential struct snd_soc_dai_link::start_dma_last
would have to be populated on sound card driver thus, had to be taken
into account in all sound card drivers. At the moment, the mchp-pdmc is
used only with simple-audio-card. In case of simple-audio-card a new DT
binding would had to be introduced to specify this action on dai-link
descriptions (as of my investigation)."
Thank you,
Claudiu
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-16 9:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 16:14 [PATCH 0/3] ASoC: mchp-pdmc: fix poc noises when starting capture Claudiu Beznea
2023-02-14 16:14 ` [PATCH 1/3] ASoC: soc-generic-dmaengine-pcm: add option to start DMA after DAI Claudiu Beznea
2023-02-14 18:14 ` Lars-Peter Clausen
2023-02-14 21:26 ` Mark Brown
2023-02-16 9:49 ` Claudiu.Beznea [this message]
2023-02-16 13:53 ` Lars-Peter Clausen
2023-02-17 10:59 ` Claudiu.Beznea
2023-02-14 16:14 ` [PATCH 2/3] ASoC: dt-bindings: sama7g5-pdmc: add microchip,startup-delay-us binding Claudiu Beznea
2023-02-16 10:04 ` Krzysztof Kozlowski
2023-02-16 10:15 ` Claudiu.Beznea
2023-02-16 10:18 ` Krzysztof Kozlowski
2023-02-16 10:41 ` Claudiu.Beznea
2023-02-16 10:43 ` Krzysztof Kozlowski
2023-02-16 14:46 ` Mark Brown
2023-02-14 16:14 ` [PATCH 3/3] ASoC: mchp-pdmc: fix poc noise at capture startup Claudiu Beznea
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=4b109846-2019-219a-262e-46f5bb504c99@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh+dt@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