| commit | 4b3269e21d50da6ce33b72f356b6714e58f7478f | |
| author | Hung-Te Lin <hungte@chromium.org> | |
| Thu, 10 Dec 2020 13:54:24 +0000 (10 21:54 +0800) | ||
| committer | Hung-Te Lin <hungte@chromium.org> | |
| Tue, 15 Dec 2020 01:51:09 +0000 (15 01:51 +0000) | ||
| tree | 9e852ab673bebefe0c7aab75a1e28ec37862138c | treesnapshot (tar.gz zip) |
| parent | 7265bab69e97a25b362d1acb0ec51970754b7f49 | commitdiff |
mb/google/kukui: help payload to identify correct speaker amp type
Kukui based devices may use different speaker amplifiers, for example
MAX98357A, RT1015, or RT1015Q/automode. To help payloads identifying
which component was installed on board, we want to pass the speaker GPIO
in different name. This can be set in Kconfig as CONFIG_SPEAKER_GPIO_NAME.
BUG=b:174534548
TEST=emerge-kukui coreboot depthcharge chromeos-bootimage
BRANCH=kukui
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Change-Id: I4b44b026bee4d3b58646eee207aea0120071dd46
Reviewed-on: https://review.coreboot.org/c/coreboot/+/48558
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Yu-Ping Wu <yupingso@google.com>
Kukui based devices may use different speaker amplifiers, for example
MAX98357A, RT1015, or RT1015Q/automode. To help payloads identifying
which component was installed on board, we want to pass the speaker GPIO
in different name. This can be set in Kconfig as CONFIG_SPEAKER_GPIO_NAME.
BUG=b:174534548
TEST=emerge-kukui coreboot depthcharge chromeos-bootimage
BRANCH=kukui
Signed-off-by: Hung-Te Lin <hungte@chromium.org>
Change-Id: I4b44b026bee4d3b58646eee207aea0120071dd46
Reviewed-on: https://review.coreboot.org/c/coreboot/+/48558
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Yu-Ping Wu <yupingso@google.com>
| src/mainboard/google/kukui/Kconfig | diffblobblamehistory | |
| src/mainboard/google/kukui/chromeos.c | diffblobblamehistory |