Skip to content

drivers: i2c: add i2c target support for ambiq soc#96059

Open
AlessandroLuo wants to merge 3 commits intozephyrproject-rtos:mainfrom
AmbiqMicro:ambiq-ios-i2c
Open

drivers: i2c: add i2c target support for ambiq soc#96059
AlessandroLuo wants to merge 3 commits intozephyrproject-rtos:mainfrom
AmbiqMicro:ambiq-ios-i2c

Conversation

@AlessandroLuo
Copy link
Copy Markdown
Contributor

Adds bingding for ambiq ios which can used as spi device or i2c target, and creates ios i2c driver.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Sep 16, 2025

The following west manifest projects have changed revision in this Pull Request:

Name Old Revision New Revision Diff

All manifest checks OK

Note: This message is automatically posted and updated by the Manifest GitHub Action.

This comment was marked as resolved.

This comment was marked as outdated.

@AlessandroLuo AlessandroLuo force-pushed the ambiq-ios-i2c branch 4 times, most recently from 51430e9 to fbebf82 Compare September 16, 2025 09:46
@sonarqubecloud
Copy link
Copy Markdown

aaronyegx
aaronyegx previously approved these changes Sep 17, 2025
Copy link
Copy Markdown
Contributor

@teburd teburd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to only implement the optional buf_read/buf_write callbacks from the ISR but these are likely the least used.

read_requested/read_processed and such are far more widely in use today.

Does this work with any of the in tree tests or samples? I'd guess it does not.

@decsny decsny removed their request for review September 18, 2025 17:31
@AlessandroLuo AlessandroLuo marked this pull request as draft September 26, 2025 08:49
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Copilot reviewed 15 out of 15 changed files in this pull request and generated 4 comments.

Comments suppressed due to low confidence (2)

drivers/spi/spi_ambiq_spid.c:1

  • The error message should clarify that exactly one child must be enabled, not just that there are 'too many'. Consider: 'IOS must have exactly one enabled child (either SPI or I2C, not both)!'
/*

drivers/i2c/i2c_ambiq_ios.c:1

  • The error message should clarify that exactly one child must be enabled, not just that there are 'too many'. Consider: 'IOS must have exactly one enabled child (either SPI or I2C, not both)!'
/*

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@github-actions github-actions bot added the Stale label Dec 20, 2025
Adds bingding for ambiq ios which can used as spi device
or i2c target, and creates ios i2c driver.

Signed-off-by: Hao Luo <hluo@ambiq.com>
Adds byte mode for i2c_ambiq_ios.

Signed-off-by: Hao Luo <hluo@ambiq.com>
Adds pm_device_get/put in i2c_ambiq_ios to support
pm_device_runtime.

Signed-off-by: Hao Luo <hluo@ambiq.com>
@sonarqubecloud
Copy link
Copy Markdown

@AlessandroLuo
Copy link
Copy Markdown
Contributor Author

This seems to only implement the optional buf_read/buf_write callbacks from the ISR but these are likely the least used.

read_requested/read_processed and such are far more widely in use today.

Does this work with any of the in tree tests or samples? I'd guess it does not.

Hi @teburd, I have added support for the byte mode as well, and ran samples\drivers\i2c\target_eeprom and tests\drivers\i2c\i2c_target_api with ambiq platforms, both passed, please help to review again, thank you.

@aescolar
Copy link
Copy Markdown
Member

Retriggering CI

@aescolar aescolar closed this Mar 16, 2026
@aescolar aescolar reopened this Mar 16, 2026
@zephyrbot zephyrbot added the area: Devicetree Binding PR modifies or adds a Device Tree binding label Mar 16, 2026
@zephyrbot zephyrbot requested a review from maass-hamburg March 16, 2026 13:02
@sonarqubecloud
Copy link
Copy Markdown

@aescolar
Copy link
Copy Markdown
Member

The CI failure is due to #85248 (comment)

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.

7 participants