From: Evan Green <evgreen@chromium.org>
To: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Mark Brown <broonie@kernel.org>
Cc: Naveen M <naveen.m@intel.com>,
Sathya Prakash <sathya.prakash.m.r@intel.com>,
Ben Zhang <benzh@chromium.org>, Rajat Jain <rajatja@chromium.org>,
Evan Green <evgreen@chromium.org>,
Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org,
Rakesh Ughreja <rakesh.a.ughreja@intel.com>,
Guenter Roeck <groeck@chromium.org>,
linux-kernel@vger.kernel.org, Yu Zhao <yuzhao@google.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Takashi Iwai <tiwai@suse.com>, Jenny TC <jenny.tc@intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jie Yang <yang.jie@linux.intel.com>
Subject: [PATCH v1 0/2] ASoC: Intel: Add Cometlake PCI IDs
Date: Mon, 6 May 2019 15:53:19 -0700 [thread overview]
Message-ID: <20190506225321.74100-1-evgreen@chromium.org> (raw)
This small series adds PCI IDs for Cometlake platforms, for a
dazzling audio experience.
Evan Green (2):
ASoC: SOF: Add Comet Lake PCI ID
ASoC: Intel: Skylake: Add Cometlake PCI IDs
sound/soc/intel/Kconfig | 9 +++++++++
sound/soc/intel/skylake/skl-messages.c | 8 ++++++++
sound/soc/intel/skylake/skl.c | 5 +++++
sound/soc/sof/intel/Kconfig | 16 ++++++++++++++++
sound/soc/sof/sof-pci-dev.c | 4 ++++
5 files changed, 42 insertions(+)
--
2.20.1
next reply other threads:[~2019-05-06 22:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 22:53 Evan Green [this message]
2019-05-06 22:53 ` [PATCH v1 1/2] ASoC: SOF: Add Comet Lake PCI ID Evan Green
2019-05-07 1:40 ` Pierre-Louis Bossart
2019-05-07 3:34 ` M R, Sathya Prakash
2019-05-07 13:37 ` [alsa-devel] " Pierre-Louis Bossart
2019-05-07 20:26 ` Pierre-Louis Bossart
2019-05-07 20:51 ` Evan Green
2019-05-07 21:06 ` Pierre-Louis Bossart
2019-05-06 22:53 ` [PATCH v1 2/2] ASoC: Intel: Skylake: Add Cometlake PCI IDs Evan Green
2019-05-06 22:56 ` [PATCH v1 0/2] ASoC: Intel: " Evan Green
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=20190506225321.74100-1-evgreen@chromium.org \
--to=evgreen@chromium.org \
--cc=alsa-devel@alsa-project.org \
--cc=benzh@chromium.org \
--cc=broonie@kernel.org \
--cc=groeck@chromium.org \
--cc=jenny.tc@intel.com \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen.m@intel.com \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rajatja@chromium.org \
--cc=rakesh.a.ughreja@intel.com \
--cc=sathya.prakash.m.r@intel.com \
--cc=tiwai@suse.com \
--cc=yang.jie@linux.intel.com \
--cc=yuzhao@google.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.