alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: fuweix.tang@intel.com
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de, liam.r.girdwood@linux.intel.com,
	Fuwei Tang <fuweix.tang@intel.com>,
	mengdong.lin@intel.com
Subject: [PATCH v1 0/3] ucm-conf: Add intel UCM conf files to alsa-ucm-conf repo
Date: Wed, 15 Mar 2017 14:47:00 +0800	[thread overview]
Message-ID: <cover.1487897097.git.fuweix.tang@intel.com> (raw)

From: Fuwei Tang <fuweix.tang@intel.com>

Add the intel UCM configs to a dedicated UCM conf repo.License can be changed to BSD
for intel files,and left as "unknown" for other conf files when they are moved from alsa-lib to
the new repo.The alsa-lib LGPL license does not cover runtime configuration files.

The configs are moved from alsa-lib repo.The original authorship and commit message of all config files will be reserved.

I write the setup code from scratch instead of copying it from Takashi in this version.

Fuwei Tang (1):
  ucm-conf: Set up for installation

Vinod Koul (2):
  ucm-conf: broxton: add broxton-rt298 conf files
  ucm-conf: skylake: add skylake-rt286 conf files

 .gitignore                       |  13 ++++
 ChangeLog                        |   1 +
 INSTALL                          |   1 +
 Makefile.am                      |   1 +
 broxton-rt298/Hdmi1              |  22 +++++++
 broxton-rt298/Hdmi2              |  14 +++++
 broxton-rt298/HiFi               | 129 +++++++++++++++++++++++++++++++++++++++
 broxton-rt298/Makefile.am        |   4 ++
 broxton-rt298/broxton-rt298.conf |  58 ++++++++++++++++++
 configure.ac                     |  24 ++++++++
 gitcompile                       |   5 ++
 skylake-rt286/Hdmi1              |  20 ++++++
 skylake-rt286/Hdmi2              |  20 ++++++
 skylake-rt286/HiFi               | 129 +++++++++++++++++++++++++++++++++++++++
 skylake-rt286/Makefile.am        |   4 ++
 skylake-rt286/skylake-rt286.conf |  60 ++++++++++++++++++
 16 files changed, 505 insertions(+)
 create mode 100644 .gitignore
 create mode 100644 ChangeLog
 create mode 120000 INSTALL
 create mode 100644 Makefile.am
 create mode 100644 broxton-rt298/Hdmi1
 create mode 100644 broxton-rt298/Hdmi2
 create mode 100644 broxton-rt298/HiFi
 create mode 100644 broxton-rt298/Makefile.am
 create mode 100644 broxton-rt298/broxton-rt298.conf
 create mode 100644 configure.ac
 create mode 100755 gitcompile
 create mode 100644 skylake-rt286/Hdmi1
 create mode 100644 skylake-rt286/Hdmi2
 create mode 100644 skylake-rt286/HiFi
 create mode 100644 skylake-rt286/Makefile.am
 create mode 100644 skylake-rt286/skylake-rt286.conf

-- 
2.7.4

             reply	other threads:[~2017-03-15  6:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15  6:47 fuweix.tang [this message]
2017-03-15  6:47 ` [PATCH v1 1/3] ucm-conf: Set up for installation fuweix.tang
2017-03-20 11:54   ` Takashi Iwai
2017-03-21  1:03     ` Tang, FuweiX
2017-03-15  6:47 ` [PATCH v1 2/3] ucm-conf: broxton: add broxton-rt298 conf files fuweix.tang
2017-03-15  6:47 ` [PATCH v1 3/3] ucm-conf: skylake: add skylake-rt286 " fuweix.tang

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.1487897097.git.fuweix.tang@intel.com \
    --to=fuweix.tang@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=mengdong.lin@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 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).