Support seems to be there in chromiumos:
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/release-R52-8350.B-chromeos-4.4/sound/soc/codecs/ts3a227e.c
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/release-R52-8350.B-chromeos-4.4/sound/soc/intel/boards/cht_bsw_max98090_ti.c
There is also ACPI that registers the audio codec apparently (grep to TI_SWITCH):
https://chromium.googlesource.com/chromiumos/third_party/coreboot/+/release-R52-8350.B/src/mainboard/google/cyan/onboard.h
https://chromium.googlesource.com/chromiumos/third_party/coreboot/+/release-R52-8350.B/src/mainboard/google/cyan/acpi/mainboard.asl
Could it be an issue with ACPI? ChromiumOS triggering different functions in ACPI compared to mainline Linux, and initializing via ACPI the codec?
Support seems to be there in chromiumos:
https:/ /chromium. googlesource. com/chromiumos/ third_party/ kernel/ +/release- R52-8350. B-chromeos- 4.4/sound/ soc/codecs/ ts3a227e. c
https:/ /chromium. googlesource. com/chromiumos/ third_party/ kernel/ +/release- R52-8350. B-chromeos- 4.4/sound/ soc/intel/ boards/ cht_bsw_ max98090_ ti.c
There is also ACPI that registers the audio codec apparently (grep to TI_SWITCH):
https:/ /chromium. googlesource. com/chromiumos/ third_party/ coreboot/ +/release- R52-8350. B/src/mainboard /google/ cyan/onboard. h
https:/ /chromium. googlesource. com/chromiumos/ third_party/ coreboot/ +/release- R52-8350. B/src/mainboard /google/ cyan/acpi/ mainboard. asl
Could it be an issue with ACPI? ChromiumOS triggering different functions in ACPI compared to mainline Linux, and initializing via ACPI the codec?