From: Pradeep Tewani <pradeep.d.tewani@intel.com>
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de, patches.audio@intel.com, broonie@kernel.org,
lgirdwood@gmail.com, Pradeep Tewani <pradeep.d.tewani@intel.com>
Subject: [PATCH v2 0/3]ASoC: Intel: Skylake: Enable hdmi for GLK
Date: Thu, 20 Jul 2017 11:40:54 +0530 [thread overview]
Message-ID: <1500531057-4286-1-git-send-email-pradeep.d.tewani@intel.com> (raw)
GLK vendor nid is different from rest of the skylake platforms. Add vendor
nid as part of driver data and use it. Also enable support for GLK
platform.
Add the patch to remove the .owner initialization in bxt driver as well
Changes in v2:
Removed the .owner field in driver
Replaced the strcmp with strncmp for bxt_rt298 probe
Pradeep Tewani (3):
ASoC: Intel: board: Remove .owner initialization in bxt_rt298 driver
ASoC: hdac_hdmi: Add the vendor nid for Geminilake HDMI
ASoC: Intel: board: Add Geminilake platform support
sound/soc/codecs/hdac_hdmi.c | 39 ++++++++++++++---
sound/soc/intel/boards/bxt_rt298.c | 85 ++++++++++++++++++++++++++++++++++++--
2 files changed, 115 insertions(+), 9 deletions(-)
--
2.7.4
next reply other threads:[~2017-07-20 6:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 6:10 Pradeep Tewani [this message]
2017-07-20 6:10 ` [PATCH v2 1/3] ASoC: Intel: board: Remove .owner initialization in bxt_rt298 driver Pradeep Tewani
2017-07-20 12:23 ` Applied "ASoC: Intel: board: Remove .owner initialization in bxt_rt298 driver" to the asoc tree Mark Brown
2017-07-20 6:10 ` [PATCH v2 2/3] ASoC: hdac_hdmi: Add the vendor nid for Geminilake HDMI Pradeep Tewani
2017-07-20 6:10 ` [PATCH v2 3/3] ASoC: Intel: board: Add Geminilake platform support Pradeep Tewani
2017-07-20 12:23 ` Applied "ASoC: Intel: board: Add Geminilake platform support" to the asoc tree Mark Brown
2017-07-20 8:26 ` [PATCH v2 0/3]ASoC: Intel: Skylake: Enable hdmi for GLK Vinod Koul
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=1500531057-4286-1-git-send-email-pradeep.d.tewani@intel.com \
--to=pradeep.d.tewani@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=patches.audio@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).