From: "Sridharan, Ranjani" <ranjani.sridharan@intel.com>
To: "broonie@kernel.org" <broonie@kernel.org>
Cc: "tiwai@suse.de" <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"bard.liao@linux.intel.com" <bard.liao@linux.intel.com>,
"pierre-louis.bossart@linux.intel.com"
<pierre-louis.bossart@linux.intel.com>
Subject: Re: Enabling DAPM for Dummy DAIs
Date: Mon, 17 Aug 2020 17:45:59 +0000 [thread overview]
Message-ID: <1a8e6e8872692ea88bd7905ed5ae0e8e2a8c0414.camel@intel.com> (raw)
In-Reply-To: <20200814123712.GB4783@sirena.org.uk>
On Fri, 2020-08-14 at 13:37 +0100, Mark Brown wrote:
> On Thu, Aug 13, 2020 at 05:21:40PM +0000, Sridharan, Ranjani wrote:
> > Hi Mark/Takashi,
>
> Please fix your mail client to word wrap within paragraphs at
> something
> substantially less than 80 columns. Doing this makes your messages
> much
> easier to read and reply to.
>
> > What would your recommendation be to get around this problem in
> > SOF? Thanks for your help.
>
> Actively using the dummy CODEC at runtime isn't a great idea at the
> best
> of times, things would be a lot easier if you used something with
> actual
> audio paths for testing - as far as I can see the issue is that
> you've
> told the system that there's nothing connected which is reasonably
> being
> interpreted as there being no need to power anything on. If you
> intend
> this to represent an actual connection it would be better to use a
> simple CODEC with no software control rather than something that
> explicitly means there is nothing connected.
Thanks, Mark. But I am still confused by what you mean by a simple
codec here. Would this simple codec be registered by the SOF platform
driver?
Thanks,
Ranjani
next prev parent reply other threads:[~2020-08-17 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 17:21 Enabling DAPM for Dummy DAIs Sridharan, Ranjani
2020-08-14 12:37 ` Mark Brown
2020-08-17 17:45 ` Sridharan, Ranjani [this message]
2020-08-17 18: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=1a8e6e8872692ea88bd7905ed5ae0e8e2a8c0414.camel@intel.com \
--to=ranjani.sridharan@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@linux.intel.com \
--cc=broonie@kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
/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).