From: han.lu@intel.com
To: broonie@kernel.org, tiwai@suse.de, vinod.koul@intel.com,
pierre-louis.bossart@linux.intel.com,
liam.r.girdwood@linux.intel.com, alsa-devel@alsa-project.org
Cc: "Lu, Han" <han.lu@intel.com>
Subject: [PATCH V5 0/2] ASoC: Add core API to register DMI names to card
Date: Tue, 5 Apr 2016 12:26:32 +0800 [thread overview]
Message-ID: <cover.1459825282.git.han.lu@intel.com> (raw)
From: "Lu, Han" <han.lu@intel.com>
Share more product information, for user space utils such as PA and UCM to
distinguish different products.
1. Add a core API to register DMI names to card.
2. Apply the API to bytcr-rt5640 driver.
changes on V5:
1. Use independent space to store card long_name, to avoid irrelavant
info sharing from card component
2. Use letter ';' instead of ':' to separate strings in long name, in
case name strings may also contain ':' and confusing user
3. Fix error that vendor name and firmware name were not optional
changes on V4:
1. Replace kmalloc() and snprintf() with ksaprintf() to simplify code
changes on V3:
1. Split the core API and the API call to two patches
2. Replace misused strcat() with snprintf()
3. Code and comment fix
Lu, Han (2):
ASoC: core: add API for registering DMI card names
ASoC: bytcr-rt5640: register DMI names for card
include/sound/soc.h | 3 ++
sound/soc/intel/boards/bytcr_rt5640.c | 13 +++++++
sound/soc/soc-core.c | 67 +++++++++++++++++++++++++++++++++++
3 files changed, 83 insertions(+)
--
2.5.0
next reply other threads:[~2016-04-05 4:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 4:26 han.lu [this message]
2016-04-05 4:26 ` [PATCH V5 1/2] ASoC: core: add API for registering DMI card names han.lu
2016-04-05 5:38 ` Takashi Sakamoto
2016-04-05 6:33 ` Takashi Sakamoto
2016-04-06 4:23 ` Han Lu
2016-04-06 5:47 ` Takashi Sakamoto
2016-04-06 6:15 ` Han Lu
2016-04-05 4:26 ` [PATCH V5 2/2] ASoC: bytcr-rt5640: register DMI names for card han.lu
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=cover.1459825282.git.han.lu@intel.com \
--to=han.lu@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=pierre-louis.bossart@linux.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 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).