From: b29396@freescale.com (Dong Aisheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/1] ASoC: soc-dapm: warn if no avaiable path found for widget kcontrol
Date: Wed, 1 Aug 2012 15:49:53 +0800 [thread overview]
Message-ID: <20120801074952.GC30492@shlinux2.ap.freescale.net> (raw)
In-Reply-To: <20120729202219.GA4384@opensource.wolfsonmicro.com>
On Mon, Jul 30, 2012 at 04:22:19AM +0800, Mark Brown wrote:
> On Fri, Jul 27, 2012 at 07:19:01PM +0800, Dong Aisheng wrote:
> > From: Dong Aisheng <dong.aisheng@linaro.org>
> >
> > This could help people know what's wrong going on if the required
> > path is not registered.
>
> This isn't a good idea, it's fairly common for widgets to have a "None"
> option which isn't expected to have an input.
>
What i changed is mux widgets, i'm wondering is it possible or correct
the mux widget has no input path?
If i understand correct, we may need set correct input path
for mux widget, or why we still need a mux?
Or can you help give an example that no input needed for mux widget?
Regards
Dong Aisheng
next prev parent reply other threads:[~2012-08-01 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 11:19 [RFC PATCH 1/1] ASoC: soc-dapm: warn if no avaiable path found for widget kcontrol Dong Aisheng
2012-07-29 20:22 ` Mark Brown
2012-08-01 7:49 ` Dong Aisheng [this message]
2012-08-01 12:15 ` Mark Brown
2012-08-02 7:08 ` Dong Aisheng
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=20120801074952.GC30492@shlinux2.ap.freescale.net \
--to=b29396@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).