[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z3vI5eJKCLfLeFwX@opensource.cirrus.com>
Date: Mon, 6 Jan 2025 12:13:25 +0000
From: Charles Keepax <ckeepax@...nsource.cirrus.com>
To: anish kumar <yesanishhere@...il.com>
CC: <lgirdwood@...il.com>, <broonie@...nel.org>, <perex@...ex.cz>,
<tiwai@...e.com>, <corbet@....net>, <linux-kernel@...r.kernel.org>,
<linux-doc@...r.kernel.org>, <linux-sound@...r.kernel.org>
Subject: Re: [PATCH V5] Docs/sound: Update codec-to-codec documentation
On Fri, Jan 03, 2025 at 10:10:25AM -0800, anish kumar wrote:
> On Thu, Dec 12, 2024 at 1:35 PM anish kumar <yesanishhere@...il.com> wrote:
> >
> > On Tue, Dec 10, 2024 at 3:06 AM Charles Keepax
> > <ckeepax@...nsource.cirrus.com> wrote:
> > >
> > > On Sat, Dec 07, 2024 at 11:34:41AM -0800, anish kumar wrote:
> > > Also what do we mean by a "A mixer must be created", I am not
> > > aware of any requirement for a mixer? The DAI link needs to be on
> > > a valid DAPM path, but I don't see any requirements other than
> > > that.
> >
> > In my case, I was implementing a mixer widget that users could
> > trigger to enable the entire DAPM path. However, I believe it's
> > sufficient to simply state that there should be a mechanism to
> > trigger the codec-to-codec widget, enabling the full DAPM path.
> > >
> Could you please confirm if this explanation is clear? If so,
> I will proceed with submitting another revision of the patch.
I am happy as long as the wording states that being on valid path
is what is required. What I am keen to remove is the explicit
reference to mixers as that is not an actual requirement.
Thanks,
Charles
Powered by blists - more mailing lists