-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[NXP] Add some common platform changes #34159
Conversation
PR #34159: Size comparison from 005f1b4 to 01406e2 Full report (6 builds for cc32xx, mbed, stm32, tizen)
|
01406e2
to
a18a7d2
Compare
PR #34159: Size comparison from 005f1b4 to a18a7d2 Full report (85 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, mbed, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where are the "legacy" files used?
Adding new files without linking in source code feels off, especially if they are "legacy" (i.e. probably should not be used anymore)?
Why do we do this? If this is to preserve old copies, why is git history not sufficient for that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not understand the "legacy" folder. The comment of Add some files in legacy folder.
in the PR summary does not help me understand them either.
Hi, @andy31415. The folder is called legacy because these files are mainly used by k32w0 (which is based on a legacy SDK). I should have specified that these files will be used by some upcoming changes. I am waiting for @chapongatien's PR related to NXP matter support submodule to be merged. Once that is done, I can clean the k32w0 further and sync what we have internally. So this is just an intermediate step and the files will eventually be used. If it is clunky, I can remove this commit for now and just keep the changes to the common NXP part. |
a18a7d2
to
c0894ce
Compare
I've removed the commits. Will add them in the future. |
PR #34159: Size comparison from 4ef104b to c0894ce Full report (85 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, mbed, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
Signed-off-by: Martin Girardot <[email protected]>
- Add StoreSoftwareUpdateCompleted API with empty implementation - Add ICD flags in common config header - Create CHIP_DEVICE_CONFIG_USE_ZEPHYR_BLE flag for BLE Zephry usage - Enclose CHIPDevicePlatformEvent header sections under CHIP_DEVICE_CONFIG_USE_ZEPHYR_BLE - Enclose lwip specific headers under CHIP_SYSTEM_CONFIG_USE_LWIP - Add temporary flag CHIP_DEVICE_CONFIG_INIT_OT_PLAT_ALARM to condition otPlatAlarmInit call. Some platforms are doing this separately and two calls will break things. - Add CHIP_DEVICE_CONFIG_PROCESS_BLE_IN_THREAD flag to override ProcessThreadActivity by extending its default implementation. Some platforms opt to do the BLE processing inside the Thread task, to avoid creating a separate BLE app task. Signed-off-by: marius-alex-tache <[email protected]>
c0894ce
to
5f7e16a
Compare
PR #34159: Size comparison from 6e31453 to 5f7e16a Full report (85 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, mbed, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
* [NXP][platform][common] Add support of boot reason Signed-off-by: Martin Girardot <[email protected]> * [NXP][platform][common] Update some components - Add StoreSoftwareUpdateCompleted API with empty implementation - Add ICD flags in common config header - Create CHIP_DEVICE_CONFIG_USE_ZEPHYR_BLE flag for BLE Zephry usage - Enclose CHIPDevicePlatformEvent header sections under CHIP_DEVICE_CONFIG_USE_ZEPHYR_BLE - Enclose lwip specific headers under CHIP_SYSTEM_CONFIG_USE_LWIP - Add temporary flag CHIP_DEVICE_CONFIG_INIT_OT_PLAT_ALARM to condition otPlatAlarmInit call. Some platforms are doing this separately and two calls will break things. - Add CHIP_DEVICE_CONFIG_PROCESS_BLE_IN_THREAD flag to override ProcessThreadActivity by extending its default implementation. Some platforms opt to do the BLE processing inside the Thread task, to avoid creating a separate BLE app task. Signed-off-by: marius-alex-tache <[email protected]> --------- Signed-off-by: Martin Girardot <[email protected]> Signed-off-by: marius-alex-tache <[email protected]> Co-authored-by: Martin Girardot <[email protected]>
* [NXP][platform][common] Add support of boot reason Signed-off-by: Martin Girardot <[email protected]> * [NXP][platform][common] Update some components - Add StoreSoftwareUpdateCompleted API with empty implementation - Add ICD flags in common config header - Create CHIP_DEVICE_CONFIG_USE_ZEPHYR_BLE flag for BLE Zephry usage - Enclose CHIPDevicePlatformEvent header sections under CHIP_DEVICE_CONFIG_USE_ZEPHYR_BLE - Enclose lwip specific headers under CHIP_SYSTEM_CONFIG_USE_LWIP - Add temporary flag CHIP_DEVICE_CONFIG_INIT_OT_PLAT_ALARM to condition otPlatAlarmInit call. Some platforms are doing this separately and two calls will break things. - Add CHIP_DEVICE_CONFIG_PROCESS_BLE_IN_THREAD flag to override ProcessThreadActivity by extending its default implementation. Some platforms opt to do the BLE processing inside the Thread task, to avoid creating a separate BLE app task. Signed-off-by: marius-alex-tache <[email protected]> --------- Signed-off-by: Martin Girardot <[email protected]> Signed-off-by: marius-alex-tache <[email protected]> Co-authored-by: Martin Girardot <[email protected]>
* [NXP][platform][common] Add support of boot reason Signed-off-by: Martin Girardot <[email protected]> * [NXP][platform][common] Update some components - Add StoreSoftwareUpdateCompleted API with empty implementation - Add ICD flags in common config header - Create CHIP_DEVICE_CONFIG_USE_ZEPHYR_BLE flag for BLE Zephry usage - Enclose CHIPDevicePlatformEvent header sections under CHIP_DEVICE_CONFIG_USE_ZEPHYR_BLE - Enclose lwip specific headers under CHIP_SYSTEM_CONFIG_USE_LWIP - Add temporary flag CHIP_DEVICE_CONFIG_INIT_OT_PLAT_ALARM to condition otPlatAlarmInit call. Some platforms are doing this separately and two calls will break things. - Add CHIP_DEVICE_CONFIG_PROCESS_BLE_IN_THREAD flag to override ProcessThreadActivity by extending its default implementation. Some platforms opt to do the BLE processing inside the Thread task, to avoid creating a separate BLE app task. Signed-off-by: marius-alex-tache <[email protected]> --------- Signed-off-by: Martin Girardot <[email protected]> Signed-off-by: marius-alex-tache <[email protected]> Co-authored-by: Martin Girardot <[email protected]>
Changes: