summaryrefslogtreecommitdiff
path: root/firmware
diff options
context:
space:
mode:
authorTom Rini <trini@konsulko.com>2017-08-22 21:51:46 -0400
committerTakashi Iwai <tiwai@suse.de>2017-08-24 18:04:29 +0200
commit9ce76511b67be8fbcdff36b7e1662e3887bb7377 (patch)
tree9735680c664bc9af560cc53d371346884426594f /firmware
parentbbba6f9d3da357bbabc6fda81e99ff5584500e76 (diff)
ASoC: rt5677: Reintroduce I2C device IDssound-4.13-rc7
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' model. [ More background note: the commit a36afb0ab648 ("ASoC: rt5677: Introduce proper table...") moved the i2c ID probed via ACPI ("RT5677CE:00") to a proper acpi_device_id table. Although the action itself is correct per se, the overseen issue is the reference id->driver_data at rt5677_i2c_probe() for retrieving the corresponding chip model for the given id. Since id=NULL is passed for ACPI matching case, we get an Oops now. We already have queued more fixes for 4.14 and they already address the issue, but they are bigger changes that aren't preferable for the late 4.13-rc stage. So, this patch just papers over the bug as a once-off quick fix for a particular ACPI matching. -- tiwai ] Fixes: a36afb0ab648 ("ASoC: rt5677: Introduce proper table for ACPI enumeration") Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Mark Brown <broonie@kernel.org> Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions