Open
Conversation
Ayush1325
force-pushed
the
i2c-transport
branch
2 times, most recently
from
7a4c5f0 to
eee4eb5
Compare
Ayush1325
added a commit
to Ayush1325/zephyr
that referenced
this pull request
Mar 5, 2026
- Add support for Zephyr I2C target API, which allows device to act as I2C slave device. - Tested using greybus-i2c transport [0]. [0]: beagleboard/greybus-zephyr#95 Signed-off-by: Ayush Singh <ayush@beagleboard.org>
The greybus node acts as a slave i2c device with an address selected by Kconfig variable. The goal is to be able to chain multiple greybus nodes over I2C. Since I2C slave cannot initiate messages to the host, cannot be used with protocols that require the node to initiate messages. Maybe we can use a GPIO to signal to host, but that would not work over grove connector. Signed-off-by: Ayush Singh <ayush@beagleboard.org>
- Fits well enough in greybus lights protocol Signed-off-by: Ayush Singh <ayush@beagleboard.org>
Ayush1325
added a commit
to Ayush1325/zephyr
that referenced
this pull request
Mar 9, 2026
- Add support for Zephyr I2C target API, which allows device to act as I2C slave device. - Tested using greybus-i2c transport [0]. [0]: beagleboard/greybus-zephyr#95 Signed-off-by: Ayush Singh <ayush@beagleboard.org>
Ayush1325
added a commit
to Ayush1325/zephyr
that referenced
this pull request
Mar 9, 2026
- Add support for Zephyr I2C target API, which allows device to act as I2C slave device. - Tested using greybus-i2c transport [0]. [0]: beagleboard/greybus-zephyr#95 Signed-off-by: Ayush Singh <ayush@beagleboard.org>
Ayush1325
added a commit
to Ayush1325/zephyr
that referenced
this pull request
Mar 9, 2026
- Add support for Zephyr I2C target API, which allows device to act as I2C slave device. - Tested using greybus-i2c transport [0]. [0]: beagleboard/greybus-zephyr#95 Signed-off-by: Ayush Singh <ayush@beagleboard.org>
Ayush1325
force-pushed
the
i2c-transport
branch
from
ff6bab2 to
43b256d
Compare
- Each color get's it's own channel. Signed-off-by: Ayush Singh <ayush@beagleboard.org>
Ayush1325
force-pushed
the
i2c-transport
branch
from
43b256d to
a61ed9a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The greybus node acts as a slave i2c device with an address selected by Kconfig variable. The goal is to be able to chain multiple greybus nodes over I2C.
Since I2C slave cannot initiate messages to the host, cannot be used with protocols that require the node to initiate messages. Maybe we can use a GPIO to signal to host, but that would not work over grove connector.