From: Takashi Iwai <tiwai@suse.de>
To: "Lin, Mengdong" <mengdong.lin@intel.com>
Cc: "liam.r.girdwood@linux.intel.com"
<liam.r.girdwood@linux.intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"mengdong.lin@linux.intel.com" <mengdong.lin@linux.intel.com>
Subject: Re: [PATCH v4 1/2] ucm: Load device-specific configuration file based on the card long name
Date: Mon, 16 Jan 2017 11:41:23 +0100 [thread overview]
Message-ID: <s5hk29vxp64.wl-tiwai@suse.de> (raw)
In-Reply-To: <F46914AEC2663F4A9BB62374E5EEF8F881A19C50@shsmsx102.ccr.corp.intel.com>
On Sun, 15 Jan 2017 11:01:15 +0100,
Lin, Mengdong wrote:
>
> > -----Original Message-----
> > From: Takashi Iwai [mailto:tiwai@suse.de]
> > Sent: Sunday, January 15, 2017 4:25 PM
> >
> > On Sat, 14 Jan 2017 09:23:55 +0100,
> > mengdong.lin@linux.intel.com wrote:
> > >
> > > From: Mengdong Lin <mengdong.lin@linux.intel.com>
> > >
> > > Intel DSP platform drivers are used by many different devices. For
> > > user space to differentiate them, ASoC machine drivers may use the DMI
> > > info
> > > (vendor-product-version-board) as card long name. Possible card long
> > > names
> > > are:
> > > DellInc.-XPS139343-01-0310JH
> > > ASUSTeKCOMPUTERINC.-T100TA-1.0-T100TA
> > > Circuitco-MinnowboardMaxD0PLATFORM-D0-MinnowBoardMAX
> > > ...
> > >
> > > And user space can define configuration files like
> > > longname\longname.conf for a specific device.
> >
> > Do you mean a file name containing a backslash?
> > I didn't find the relevant code in your patch...
>
> No, the file name doesn't contain a backslash. It means we're using the card long name as both the directory name that contains the UCM config file and the name of the config file itself.
> E.g. for the laptop Dell XPS 13, UCM will try to find a directory "DellInc.-XPS139343-01-0310JH", and then find the file " DellInc.-XPS139343-01-0310JH.conf" under the directory. If it cannot find the this file, it will fall back to open file "broadwell-rt286.conf" under directory "broadwell-rt286".
Ah, a backslash as on DOS. Use a slash for Linux instead :)
Takashi
next prev parent reply other threads:[~2017-01-16 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 8:23 [PATCH v4 0/2] ucm: Automatically load the best config file based on the card long name mengdong.lin
2017-01-14 8:23 ` [PATCH v4 1/2] ucm: Load device-specific configuration " mengdong.lin
2017-01-15 8:25 ` Takashi Iwai
2017-01-15 10:01 ` Lin, Mengdong
2017-01-16 10:41 ` Takashi Iwai [this message]
2017-01-18 3:52 ` Lin, Mengdong
2017-01-14 8:24 ` [PATCH v4 2/2] ucm: Add command 'get _file' to get the config file name of the opened card mengdong.lin
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=s5hk29vxp64.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=mengdong.lin@intel.com \
--cc=mengdong.lin@linux.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.