Skip to content

Conversation

ck-telecom
Copy link
Contributor

Add i2c driver for sf32lb platform

@ck-telecom ck-telecom force-pushed the sf32lb_i2c branch 6 times, most recently from 5410670 to e1dcf08 Compare September 22, 2025 07:26
@ck-telecom ck-telecom force-pushed the sf32lb_i2c branch 7 times, most recently from 7ef9f77 to e740c36 Compare September 26, 2025 07:52
@gmarull
Copy link
Member

gmarull commented Oct 14, 2025

@ck-telecom any progress on this? we're interested to move this forward as we need to talk to some I2C devices :-)

@ck-telecom
Copy link
Contributor Author

ck-telecom commented Oct 15, 2025

@ck-telecom any progress on this? we're interested to move this forward as we need to talk to some I2C devices :-)

I tried a few times with my ft6146 driver(#96330), the iic bus SR show EBB(EarlyBusBusy), and I check with my analyzer, there is no signal, but the driver could work with my former sifli-hal based driver as I tested OK, so for now it get stucked, I could open the review but need debug

Add i2c device controller for sf32lb platform

Signed-off-by: Qingsong Gou <[email protected]>
Add i2c device controller for sf32lb platform

Signed-off-by: Qingsong Gou <[email protected]>
@ck-telecom ck-telecom marked this pull request as ready for review October 16, 2025 08:43
@ck-telecom
Copy link
Contributor Author

@ck-telecom any progress on this? we're interested to move this forward as we need to talk to some I2C devices :-)

I tried a few times with my ft6146 driver(#96330), the iic bus SR show EBB(EarlyBusBusy), and I check with my analyzer, there is no signal, but the driver could work with my former sifli-hal based driver as I tested OK, so for now it get stucked, I could open the review but need debug

fixed

@ck-telecom ck-telecom force-pushed the sf32lb_i2c branch 2 times, most recently from f4d7306 to a84754c Compare October 16, 2025 12:30
@ck-telecom
Copy link
Contributor Author

@ck-telecom any progress on this? we're interested to move this forward as we need to talk to some I2C devices :-)

i2c poll method tested with ft6146 touch driver

[00:04:58.771,000] <dbg> ft6146: ft6146_process_touch: touch_num: 1
[00:04:58.771,000] <dbg> ft6146: ft6146_process_touch: event_flag:2, id:0, x:182, y:249
[00:04:58.771,000] <dbg> input: input_report: Timeout discarded. No blocking in syswq.
[00:04:58.771,000] <dbg> input: input_report: Timeout discarded. No blocking in syswq.
[00:04:58.771,000] <dbg> input: input_report: Timeout discarded. No blocking in syswq.

[00:04:58.782,000] <dbg> ft6146: ft6146_process_touch: touch_num: 1
[00:04:58.782,000] <dbg> ft6146: ft6146_process_touch: event_flag:2, id:0, x:182, y:249
[00:04:58.782,000] <dbg> input: input_report: Timeout discarded. No blocking in syswq.
[00:04:58.782,000] <dbg> input: input_report: Timeout discarded. No blocking in syswq.
[00:04:58.782,000] <dbg> input: input_report: Timeout discarded. No blocking in syswq.

@ck-telecom ck-telecom force-pushed the sf32lb_i2c branch 3 times, most recently from 62e19f0 to 64ca885 Compare October 18, 2025 13:21
Add i2c driver for sf32lb platform

Signed-off-by: Qingsong Gou <[email protected]>
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants