All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mengdong Lin <mengdong.lin@linux.intel.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
	mengdong.lin@intel.com, liam.r.girdwood@linux.intel.com,
	broonie@kernel.org, pierre-louis.bossart@intel.com
Subject: Re: [RFC PATCH] ucm: Add support for device positions
Date: Tue, 3 Jan 2017 18:09:26 +0800	[thread overview]
Message-ID: <586B7856.6090005@linux.intel.com> (raw)
In-Reply-To: <20170103082143.GF3573@localhost>



On 01/03/2017 04:21 PM, Vinod Koul wrote:
> On Tue, Jan 03, 2017 at 02:09:18PM +0800, mengdong.lin@linux.intel.com wrote:
>> From: Mengdong Lin <mengdong.lin@linux.intel.com>
>>
>> Users can provide prosition info of audio devices as a device value. This
>> will help the sound server to choose an audio devices from some candidates
>> based on the their locations and the status of the machine.
>
> This is good thing to have but some bits are bit unclear to me atm. When you
> say device, do you mean sound card?

No, the device here does not mean a sound card, but mean an I/O device 
like speaker or dmic, defined by 'SectionDevice'.

> For me, position makes sense for dmics and speakers. So can you help me out
> by understanding how we can describe these...
>

For example, if there are two DMICs, one is in the front and one on the 
back, we can define their positions as below:

SectionDevice."MainMIC" {

        ...

         EnableSequence [
                ...
         ]

         DisableSequence [
                 ...
         ]

         Value {
                 Position "Front"
         }
}

SectionDevice."SecondaryMIC" {

	...

	EnableSequence [
	...
	]

	DisableSequence [
	...
	]

	Value {
		Position "Back"
	}
}


Thanks
Mengdong

  reply	other threads:[~2017-01-03 10:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03  6:09 [RFC PATCH] ucm: Add support for device positions mengdong.lin
2017-01-03  8:21 ` Vinod Koul
2017-01-03 10:09   ` Mengdong Lin [this message]
2017-01-03 14:50     ` Pierre-Louis Bossart
2017-01-03 15:06       ` Liam Girdwood
2017-01-03 14:58 ` Liam Girdwood
2017-01-03 15:32   ` Lin, Mengdong

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=586B7856.6090005@linux.intel.com \
    --to=mengdong.lin@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=mengdong.lin@intel.com \
    --cc=pierre-louis.bossart@intel.com \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@intel.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.