[lkml]   [2017]   [Aug]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
Subject[PATCH] ASoC: rt5677: Reintroduce I2C device IDs
Not all devices with ACPI and this combination of sound devices will
have the required information provided via ACPI. Reintroduce the I2C
device ID to restore sound functionality on on the Chromebook 'Samus'

Fixes: a36afb0ab648 ("ASoC: rt5677: Introduce proper table for ACPI enumeration")
Cc: Bard Liao <>
Cc: Oder Chiou <>
Cc: Liam Girdwood <>
Cc: Jaroslav Kysela <>
Cc: Takashi Iwai <>
Cc: Andy Shevchenko <>
Cc: Mark Brown <>
Cc: Linus Torvalds <>
Signed-off-by: Tom Rini <>
This is a regression from v4.12 on my laptop (a Chromebook 'Samus'
that's not running ChromeOS). My fault for getting out of the habit of
trying -rc1 when it comes out and not spotting this sooner. I'm not
100% sure if this fix is correct for all cases as I'm only able to test
my hardware here, and this does fix my laptop.
sound/soc/codecs/rt5677.c | 1 +
1 file changed, 1 insertion(+)

diff --git a/sound/soc/codecs/rt5677.c b/sound/soc/codecs/rt5677.c
index 36e530a36c82..6f629278d982 100644
--- a/sound/soc/codecs/rt5677.c
+++ b/sound/soc/codecs/rt5677.c
@@ -5021,6 +5021,7 @@ static int rt5677_write(void *context, unsigned int reg, unsigned int val)
static const struct i2c_device_id rt5677_i2c_id[] = {
{ "rt5677", RT5677 },
{ "rt5676", RT5676 },
+ { "RT5677CE:00", RT5677 },
{ }
MODULE_DEVICE_TABLE(i2c, rt5677_i2c_id);
 \ /
  Last update: 2017-08-23 03:53    [W:0.208 / U:4.640 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site