Attention is currently required from: Hung-Te Lin, Paul Menzel, Xi Chen, Yidi Lin, Yu-Ping Wu.
Vince Liu has posted comments on this change by Vince Liu. ( https://review.coreboot.org/c/coreboot/+/87352?usp=email )
Change subject: soc/mediatek/common: Move I2C functions to common code
......................................................................
Patch Set 5:
(1 comment)
File src/soc/mediatek/common/include/soc/i2c_v1.h:
PS1:
I'm fine with that as well.
How about using the existing `I2C_FAST_SPEED` (i.e., 400KHz) instead of a new dummy speed? I've checked that all other legacy platforms use this speed in `mtk_i2c_bus_init(uint8_t bus)`. We could simply use `assert(speed == I2C_SPEED_FAST)` for validation without altering the existing implementation of `mtk_i2c_bus_init(uint8_t bus)`. What do you guys think?
--
To view, visit
https://review.coreboot.org/c/coreboot/+/87352?usp=email
To unsubscribe, or for help writing mail filters, visit
https://review.coreboot.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: coreboot
Gerrit-Branch: main
Gerrit-Change-Id: I6ac7009f5af4e6379d3f73aec61d0f4abd28471c
Gerrit-Change-Number: 87352
Gerrit-PatchSet: 5
Gerrit-Owner: Vince Liu
vince-wl.liu@mediatek.com
Gerrit-Reviewer: Hung-Te Lin
hungte@chromium.org
Gerrit-Reviewer: Paul Menzel
paulepanter@mailbox.org
Gerrit-Reviewer: Xi Chen
xixi.chen@mediatek.com
Gerrit-Reviewer: Yidi Lin
yidilin@google.com
Gerrit-Reviewer: Yu-Ping Wu
yupingso@google.com
Gerrit-Reviewer: build bot (Jenkins)
no-reply@coreboot.org
Gerrit-Attention: Xi Chen
xixi.chen@mediatek.com
Gerrit-Attention: Hung-Te Lin
hungte@chromium.org
Gerrit-Attention: Paul Menzel
paulepanter@mailbox.org
Gerrit-Attention: Yu-Ping Wu
yupingso@google.com
Gerrit-Attention: Yidi Lin
yidilin@google.com
Gerrit-Comment-Date: Mon, 21 Apr 2025 14:52:59 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: Paul Menzel
paulepanter@mailbox.org
Comment-In-Reply-To: Vince Liu
vince-wl.liu@mediatek.com
Comment-In-Reply-To: Yu-Ping Wu
yupingso@google.com
Comment-In-Reply-To: Yidi Lin
yidilin@google.com