Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Features/add icm456xx #9

Merged
merged 1 commit into from
Apr 4, 2025

Conversation

afontaine-invn
Copy link
Collaborator

@afontaine-invn afontaine-invn commented Mar 4, 2025

Support ICM45686 sensor from the icm456xx family
Update README, Cmakelist and drivers folder

* Added ICM45686 in README.md
* Update ICM456xx driver (Newport A) version to 2.4.0 icm45605_github package
Update inv_imu .h to support different variants
* Fix https://invensense.atlassian.net/browse/SWNEW-612
---------

Co-authored-by: JH Kim <jh.kim@tdk.com>
@afontaine-invn afontaine-invn changed the title Features/add icm456xx (#12) Features/add icm456xx Mar 4, 2025
@afontaine-invn afontaine-invn self-assigned this Mar 4, 2025
@afontaine-invn
Copy link
Collaborator Author

afontaine-invn commented Mar 17, 2025

Hi @nashif , hi @thelinuxfoundation, hi @stephanosio , hi @carlescufi, do you have any chances to review and add approval?

I'm usually maintainer of the tdk_hal so this time I cannot do the review myself.
And I don't understand why the collaborators defined are not put in reviewers.
https://github.com/zephyrproject-rtos/zephyr/blob/0136c2af78f3cda6c0799b8564a485717522b76c/MAINTAINERS.yml#L5102

Comment on lines +23 to +37
/** @brief Function pointer to read register(s).
* @param[in] reg Register address to be read.
* @param[out] buf Output data from the register.
* @param[in] len Number of byte to be read.
* @return 0 on success, negative value on error.
*/
typedef int (*inv_imu_read_reg_t)(void * context, uint8_t reg, uint8_t *buf, uint32_t len);

/** @brief Function pointer to write register(s).
* @param[in] reg Register address to be written.
* @param[in] buf Input data to write.
* @param[in] len Number of byte to be written.
* @return 0 on success, negative value on error.
*/
typedef int (*inv_imu_write_reg_t)(void * context, uint8_t reg, const uint8_t *buf, uint32_t len);
Copy link
Member

Choose a reason for hiding this comment

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

Same question I think I've left in another PR: how will this work with async transfers? (e.g: Streaming mode). Is there async variant that provides the result through a callback?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

For sure, with the current driver version, async transfer is not supported. We currently use a callback at higher level to be notified in case of FIFO interrupt for example.
But I start to understand that this is a crucial question for next sensor driver generation, so we need to dig into v2 version and think about how to be able to support such case.

Copy link
Member

Choose a reason for hiding this comment

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

Ok, please keep in mind the upstreamed version of ICM45686 already supports v2: https://github.com/zephyrproject-rtos/zephyr/tree/main/drivers/sensor/tdk/icm45686

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Hi @ubieda , I'm still stuck to merge this. Could you approve it? As said above, the reviewers should be tdk folks but it is zephyr members who are not really available I supposed ... I don't know how to move forward.

@ubieda
Copy link
Member

ubieda commented Apr 3, 2025

@afontaine-invn as you can see, my +1 does not count towards the requirements. @rbuisson-invn please review this PR as it seems you have collaborator access to this HAL repo.

@afontaine-invn
Copy link
Collaborator Author

afontaine-invn commented Apr 3, 2025

Hi @nashif , hi @thelinuxfoundation, hi @stephanosio , hi @carlescufi, could you help to merge this PR as it seems you are the only ones to be able to do so?

There is an issue with the PR process here. Do you know who I should ping to get it resolve?

@ubieda
Copy link
Member

ubieda commented Apr 3, 2025

@kartben it seems the TDK team does not have the rights to approve their own HAL PRs. According to zephyrproject-rtos/zephyr#71561 the following users should have R/W access:

Maintainership

tdk_hal will be maintained by:

Could you help us over here? Thanks!

@nashif
Copy link
Member

nashif commented Apr 3, 2025

@afontaine-invn you should be able to merge this now.

@afontaine-invn afontaine-invn merged commit 1e9a9e8 into zephyrproject-rtos:main Apr 4, 2025
@afontaine-invn
Copy link
Collaborator Author

Thanks !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants