All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: anish kumar <yesanishhere@gmail.com>
Cc: <lgirdwood@gmail.com>, <broonie@kernel.org>, <perex@perex.cz>,
	<tiwai@suse.com>, <corbet@lwn.net>,
	<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
	<linux-sound@vger.kernel.org>
Subject: Re: [PATCH V5] Docs/sound: Update codec-to-codec documentation
Date: Mon, 6 Jan 2025 12:13:25 +0000	[thread overview]
Message-ID: <Z3vI5eJKCLfLeFwX@opensource.cirrus.com> (raw)
In-Reply-To: <CABCoZhAqhUxJSrELx1if1QYQK0wt_wrHMVcPwVbkRoqmHA2==A@mail.gmail.com>

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@gmail.com> wrote:
> >
> > On Tue, Dec 10, 2024 at 3:06 AM Charles Keepax
> > <ckeepax@opensource.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

  reply	other threads:[~2025-01-06 12:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-07 19:34 [PATCH V5] Docs/sound: Update codec-to-codec documentation anish kumar
2024-12-10 11:06 ` Charles Keepax
2024-12-12 21:35   ` anish kumar
2025-01-03 18:10     ` anish kumar
2025-01-06 12:13       ` Charles Keepax [this message]
2024-12-10 12:54 ` 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=Z3vI5eJKCLfLeFwX@opensource.cirrus.com \
    --to=ckeepax@opensource.cirrus.com \
    --cc=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=lgirdwood@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=yesanishhere@gmail.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 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.