From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bard Liao <bardliao@realtek.com>,
Oder Chiou <oder_chiou@realtek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
alsa-devel@alsa-project.org, John Keeping <john@metanate.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v2 0/3] ASoC: rt5677: Move platform code to where it belongs
Date: Thu, 15 Jun 2017 15:46:35 +0300 [thread overview]
Message-ID: <20170615124638.65971-1-andriy.shevchenko@linux.intel.com> (raw)
There are few issues with current approach:
- ACPI enumeration should be done by IDs, and not by instances
- Platform code with board related stuff should reside in corresponding module
Fix those issues here.
Andy Shevchenko (3):
ASoC: rt5677: Introduce proper table for ACPI enumeration
ASoC: rt5677: Move platform code to board file
ASoC: Intel: bdw-rt5677: Switch to devm_acpi_dev_add_driver_gpios()
sound/soc/codecs/rt5677.c | 32 +++++++-------------------------
sound/soc/intel/boards/bdw-rt5677.c | 26 ++++++++++++++++++++++++++
2 files changed, 33 insertions(+), 25 deletions(-)
--
2.11.0
next reply other threads:[~2017-06-15 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 12:46 Andy Shevchenko [this message]
2017-06-15 12:46 ` [PATCH v2 1/3] ASoC: rt5677: Introduce proper table for ACPI enumeration Andy Shevchenko
2017-06-15 12:46 ` [PATCH v2 2/3] ASoC: rt5677: Move platform code to board file Andy Shevchenko
2017-06-16 16:53 ` Applied "ASoC: rt5677: Move platform code to board file" to the asoc tree Mark Brown
2017-06-15 12:46 ` [PATCH v2 3/3] ASoC: Intel: bdw-rt5677: Switch to devm_acpi_dev_add_driver_gpios() Andy Shevchenko
2017-06-16 17:50 ` Applied "ASoC: Intel: bdw-rt5677: Switch to devm_acpi_dev_add_driver_gpios()" to the asoc tree Mark Brown
2017-06-15 12:49 ` [PATCH v2 0/3] ASoC: rt5677: Move platform code to where it belongs Andy Shevchenko
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=20170615124638.65971-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=john@metanate.com \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.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).