From: Mark Brown <broonie@kernel.org> To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> Cc: Codrin.Ciubotariu@microchip.com, alsa-devel@alsa-project.org, lgirdwood@gmail.com, linux-kernel@vger.kernel.org, tiwai@suse.com, gustavoars@kernel.org, mirq-linux@rere.qmqm.pl Subject: Re: [RFC PATCH 0/3] Separate BE DAI HW constraints from FE ones Date: Mon, 19 Apr 2021 16:07:05 +0100 [thread overview] Message-ID: <20210419150705.GB5645@sirena.org.uk> (raw) In-Reply-To: <dfcf8b69-6ede-7344-79c0-cb572e03359c@linux.intel.com> [-- Attachment #1: Type: text/plain, Size: 794 bytes --] On Fri, Apr 16, 2021 at 02:39:25PM -0500, Pierre-Louis Bossart wrote: > On 4/16/21 1:55 PM, Mark Brown wrote: > > to the maximum supported bit width for internal operation so bit width > > only matters on external interfaces) but I think for a first pass we can > > get away with forcing everything other than what DPCM has as front ends > > into static configurations. > You lost me on the last sentence. did you mean "forcing everything into > static configurations except for what DPCM has as front-ends"? Yes... > It may already be too late for static configurations, Intel, NXP and others > have started to enable cases where the dailink configuration varies. Well, they won't be able to use any new stuff until someone implements support for dynamic configurations in the new stuff. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org> To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> Cc: alsa-devel@alsa-project.org, gustavoars@kernel.org, lgirdwood@gmail.com, linux-kernel@vger.kernel.org, tiwai@suse.com, Codrin.Ciubotariu@microchip.com, mirq-linux@rere.qmqm.pl Subject: Re: [RFC PATCH 0/3] Separate BE DAI HW constraints from FE ones Date: Mon, 19 Apr 2021 16:07:05 +0100 [thread overview] Message-ID: <20210419150705.GB5645@sirena.org.uk> (raw) In-Reply-To: <dfcf8b69-6ede-7344-79c0-cb572e03359c@linux.intel.com> [-- Attachment #1: Type: text/plain, Size: 794 bytes --] On Fri, Apr 16, 2021 at 02:39:25PM -0500, Pierre-Louis Bossart wrote: > On 4/16/21 1:55 PM, Mark Brown wrote: > > to the maximum supported bit width for internal operation so bit width > > only matters on external interfaces) but I think for a first pass we can > > get away with forcing everything other than what DPCM has as front ends > > into static configurations. > You lost me on the last sentence. did you mean "forcing everything into > static configurations except for what DPCM has as front-ends"? Yes... > It may already be too late for static configurations, Intel, NXP and others > have started to enable cases where the dailink configuration varies. Well, they won't be able to use any new stuff until someone implements support for dynamic configurations in the new stuff. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-04-19 15:07 UTC|newest] Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-23 11:43 [RFC PATCH 0/3] Separate BE DAI HW constraints from FE ones Codrin Ciubotariu 2021-03-23 11:43 ` Codrin Ciubotariu 2021-03-23 11:43 ` [RFC PATCH 1/3] pcm: use substream instead of runtime in snd_pcm_hw_rule_add() Codrin Ciubotariu 2021-03-23 11:43 ` Codrin Ciubotariu 2021-03-23 11:43 ` [RFC PATCH 2/3] ASoC: soc-pcm: add hw_constraints for BE DAI links Codrin Ciubotariu 2021-03-23 11:43 ` Codrin Ciubotariu 2021-03-23 11:43 ` [RFC PATCH 3/3] ASoC: soc-pcm: apply BE HW constraint rules Codrin Ciubotariu 2021-03-23 11:43 ` Codrin Ciubotariu 2021-03-23 12:15 ` [RFC PATCH 0/3] Separate BE DAI HW constraints from FE ones Jaroslav Kysela 2021-03-23 12:15 ` Jaroslav Kysela 2021-03-23 14:18 ` Codrin.Ciubotariu 2021-03-23 14:18 ` Codrin.Ciubotariu 2021-04-14 14:58 ` Codrin.Ciubotariu 2021-04-14 14:58 ` Codrin.Ciubotariu 2021-04-15 16:17 ` Mark Brown 2021-04-15 16:17 ` Mark Brown 2021-04-15 16:56 ` Codrin.Ciubotariu 2021-04-15 16:56 ` Codrin.Ciubotariu 2021-04-15 17:25 ` Mark Brown 2021-04-15 17:25 ` Mark Brown 2021-04-16 16:03 ` Codrin.Ciubotariu 2021-04-16 16:03 ` Codrin.Ciubotariu 2021-04-16 16:31 ` Mark Brown 2021-04-16 16:31 ` Mark Brown 2021-04-16 16:47 ` Pierre-Louis Bossart 2021-04-16 16:47 ` Pierre-Louis Bossart 2021-04-16 18:55 ` Mark Brown 2021-04-16 18:55 ` Mark Brown 2021-04-16 19:39 ` Pierre-Louis Bossart 2021-04-16 19:39 ` Pierre-Louis Bossart 2021-04-19 15:07 ` Mark Brown [this message] 2021-04-19 15:07 ` Mark Brown 2021-04-16 17:39 ` Codrin.Ciubotariu 2021-04-16 17:39 ` Codrin.Ciubotariu 2021-03-23 19:25 ` Pierre-Louis Bossart 2021-03-23 19:25 ` Pierre-Louis Bossart 2021-03-24 9:51 ` Codrin.Ciubotariu 2021-03-24 9:51 ` Codrin.Ciubotariu 2021-03-24 15:28 ` Pierre-Louis Bossart 2021-03-24 15:28 ` Pierre-Louis Bossart 2021-03-24 17:12 ` Codrin.Ciubotariu 2021-03-24 17:12 ` Codrin.Ciubotariu
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=20210419150705.GB5645@sirena.org.uk \ --to=broonie@kernel.org \ --cc=Codrin.Ciubotariu@microchip.com \ --cc=alsa-devel@alsa-project.org \ --cc=gustavoars@kernel.org \ --cc=lgirdwood@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=mirq-linux@rere.qmqm.pl \ --cc=pierre-louis.bossart@linux.intel.com \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.