diff options
author | Hans de Goede <hdegoede@redhat.com> | 2022-03-07 18:38:44 +0100 |
---|---|---|
committer | Lee Jones <lee.jones@linaro.org> | 2022-03-23 14:51:51 +0000 |
commit | 9ed55e9ac536a3d60e5dd75def3e9158d1d09f5e (patch) | |
tree | 6f2eba86779df6bc56dee296994e81d7bf971ef2 /.cocciconfig | |
parent | 3cf2b4344b651b94d62411963e666c9cb5b99e62 (diff) | |
download | linux-9ed55e9ac536a3d60e5dd75def3e9158d1d09f5e.tar.bz2 |
mfd: arizona-spi: Add Android board ACPI table handling
x86/ACPI boards with an arizona WM5102 codec ship with either Windows or
Android as factory installed OS.
The ACPI fwnode for the codec on Android boards misses 2 things compared
to the Windows boards (this is hardcoded in the Android board kernels):
1. There is no CLKE ACPI method to enabe the 32 KHz clock the codec needs
for jack-detection.
2. The GPIOs used by the codec are not listed in the fwnode for the codec.
The ACPI tables on x86/ACPI boards shipped with Android being incomplete
happens a lot. The special drivers/platform/x86/x86-android-tablets.c
module contains DMI based per model handling to compensate for this.
This module will enable the 32KHz clock through the pinctrl framework
to fix 1. and it will also register a gpio-lookup table for all GPIOs
needed by the codec + machine driver, including the GPIOs coming from
the codec itself.
Add an arizona_spi_acpi_android_probe() function which waits for the
x86-android-tablets to have set things up before continue with probing
the arizona WM5102 codec.
Acked-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Lee Jones <lee.jones@linaro.org>
Link: https://lore.kernel.org/r/20220307173844.199135-2-hdegoede@redhat.com
Diffstat (limited to '.cocciconfig')
0 files changed, 0 insertions, 0 deletions