linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Keeping <john@metanate.com>
To: alsa-devel@alsa-project.org
Cc: linux-kernel@vger.kernel.org, Jie Yang <yang.jie@linux.intel.com>,
	Bard Liao <bardliao@realtek.com>,
	Oder Chiou <oder_chiou@realtek.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>, Ben Zhang <benzh@chromium.org>,
	Dylan Reid <dgreid@chromium.org>,
	John Keeping <john@metanate.com>
Subject: [PATCH 0/2] ASoC: Chromebook Pixel 2015 support
Date: Sun, 14 Aug 2016 12:18:21 +0100	[thread overview]
Message-ID: <20160814111823.1782-1-john@metanate.com> (raw)

These patches add basic support for audio on the Chromebook Pixel 2015.
I took the machine driver from ChromeOS commit v3.14-10186-g7e7d95df2983
and other than removing support for wake on voice (which is not
supported by the mainline rt5677 codec driver), the only differences are
to cope with API changes since 3.14.

Only two authors have committed changes to the machine driver in the
ChromeOS tree and all of the commits are signed off; both authors' SoB
lines are preserved in the second commit here.

The codec driver is sufficiently different that I just added ACPI
support from scratch using the ChromeOS source as a reference for the
property names.

John Keeping (2):
  ASoC: rt5677: Add ACPI support
  ASoC: Intel: boards: Add bdw-rt5677 machine driver

 sound/soc/codecs/rt5677.c           | 109 +++++++++---
 sound/soc/intel/Kconfig             |  11 ++
 sound/soc/intel/boards/Makefile     |   2 +
 sound/soc/intel/boards/bdw-rt5677.c | 341 ++++++++++++++++++++++++++++++++++++
 sound/soc/intel/common/sst-acpi.c   |   1 +
 5 files changed, 443 insertions(+), 21 deletions(-)
 create mode 100644 sound/soc/intel/boards/bdw-rt5677.c

-- 
2.9.3.728.g30b24b4.dirty

             reply	other threads:[~2016-08-14 11:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-14 11:18 John Keeping [this message]
2016-08-14 11:18 ` [PATCH 1/2] ASoC: rt5677: Add ACPI support John Keeping
2016-08-16 17:20   ` Mark Brown
2016-08-17 10:05     ` John Keeping
2016-08-14 11:18 ` [PATCH 2/2] ASoC: Intel: boards: Add bdw-rt5677 machine driver John Keeping
2016-08-17 16:20   ` John Keeping
2016-08-24 21:06 ` [PATCH v2 0/2] ASoC: Chromebook Pixel 2015 audio support John Keeping
2016-08-24 21:06   ` [PATCH v2 1/2] ASoC: rt5677: Add ACPI support John Keeping
2016-08-29 12:24     ` Tom Rini
2016-09-25  5:57     ` Applied "ASoC: rt5677: Add ACPI support" to the asoc tree Mark Brown
2016-08-24 21:06   ` [PATCH v2 2/2] ASoC: Intel: boards: Add bdw-rt5677 machine driver John Keeping
2016-08-29 12:25     ` Tom Rini
2016-09-25  5:57     ` Applied "ASoC: Intel: boards: Add bdw-rt5677 machine driver" to the asoc tree Mark Brown
2016-09-05 14:34   ` [PATCH v2 0/2] ASoC: Chromebook Pixel 2015 audio support John Keeping
2016-09-14 13:11     ` Mark Brown

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=20160814111823.1782-1-john@metanate.com \
    --to=john@metanate.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bardliao@realtek.com \
    --cc=benzh@chromium.org \
    --cc=broonie@kernel.org \
    --cc=dgreid@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oder_chiou@realtek.com \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=yang.jie@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 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).