From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
Tanu Kaskinen <tanu.kaskinen@linux.intel.com>,
Mark Brown <broonie@kernel.org>,
Arun Raghavan <arun@accosted.net>, Han Lu <han.lu@intel.com>
Subject: Re: Separate input and output jacks for one UCM device?
Date: Thu, 02 Apr 2015 07:39:10 +0100 [thread overview]
Message-ID: <1427956750.6532.11.camel@loki> (raw)
In-Reply-To: <CAN8cciYU-KKSUhYQZgvqLHdAQFtBnpwaDtJ1K_fRwEROM-PRdg@mail.gmail.com>
On Thu, 2015-04-02 at 07:24 +0800, Raymond Yau wrote:
> > > > >
> > > >
> > > > I've added a few others on the CC that would be interested.
> > > >
> > > > > My understanding is that a UCM device can represent a thing
> that has
> > > > > both input and output (I don't particularly like that, but
> it's too late
> > > > > to complain).
> > > >
> > > > Yes, but it can also represent simplex devices too e.g.
> > > > "Headset-Speakers" and "Headset-Mic". There are not any hard
> rules here,
> > > > but most examples are using duplex devices as historically UCM
> came from
> > > > the phone ecosystem use cases.
>
> On some mobile phones which have FM radio , how do UCM handle FM radio
> since it need to use the headphone as antenna ?
This use case is just treated like any other where we have to set the
proper kcontrols and devices in the UCM config. This would include the
headphone if required for audio playback or antenna.
Liam
next prev parent reply other threads:[~2015-04-02 6:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 19:41 Separate input and output jacks for one UCM device? Tanu Kaskinen
2015-03-19 9:15 ` Liam Girdwood
2015-03-19 14:09 ` Takashi Iwai
2015-03-19 14:19 ` Mark Brown
2015-03-19 14:22 ` Jie, Yang
2015-03-19 14:34 ` Takashi Iwai
2015-03-19 14:31 ` Jie, Yang
2015-03-19 14:37 ` Takashi Iwai
2015-03-19 14:42 ` Mark Brown
2015-03-19 14:51 ` Takashi Iwai
2015-03-19 15:18 ` Mark Brown
2015-03-19 15:28 ` Takashi Iwai
2015-03-19 15:45 ` Mark Brown
2015-03-20 4:03 ` Raymond Yau
2015-03-31 16:49 ` Tanu Kaskinen
2015-04-01 12:27 ` Liam Girdwood
2015-04-01 16:56 ` Tanu Kaskinen
2015-04-01 23:24 ` Raymond Yau
2015-04-02 6:39 ` Liam Girdwood [this message]
2015-04-02 15:28 ` Dylan Reid
2015-04-04 5:39 ` Raymond Yau
2015-04-06 9:26 ` Liam Girdwood
2015-04-07 3:00 ` Raymond Yau
2015-04-08 1:29 ` Raymond Yau
2015-04-07 20:37 ` Tanu Kaskinen
2015-04-15 15:39 ` Tanu Kaskinen
2015-04-15 16:10 ` Dylan Reid
2015-04-16 8:31 ` Tanu Kaskinen
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=1427956750.6532.11.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=arun@accosted.net \
--cc=broonie@kernel.org \
--cc=han.lu@intel.com \
--cc=superquad.vortex2@gmail.com \
--cc=tanu.kaskinen@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 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.