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

manifest: Update to latest upstream #91

Merged

Conversation

jerome-pouiller
Copy link
Contributor

Support for 917 is now a part of the upstream.

@jerome-pouiller jerome-pouiller force-pushed the align-with-upstream branch 5 times, most recently from 337be93 to 7fd89db Compare February 11, 2025 17:13
Comment on lines 39 to 74
- name: Build Entropy test
working-directory: zephyr-silabs
shell: bash
run: |
west twister -v --inline-logs -K \
-s drivers.entropy \
-p siwx917_rb4338a

- name: Build Flash test
working-directory: zephyr-silabs
shell: bash
run: |
west twister -v --inline-logs \
-s drivers.flash.common.default \
-p siwx917_rb4338a \
-x DTC_OVERLAY_FILE=$(pwd)/tests/drivers/flash/common/boards/siwx917_rb4338a.overlay

- name: Build DMA test
working-directory: zephyr-silabs
shell: bash
run: |
west twister -v --inline-logs \
-s drivers.dma.chan_blen_transfer \
-p siwx917_rb4338a \
-x DTC_OVERLAY_FILE=$(pwd)/tests/drivers/dma/chan_blen_transfer/boards/siwx917_rb4338a.overlay \
-x EXTRA_CONF_FILE=$(pwd)/tests/drivers/dma/chan_blen_transfer/boards/siwx917_rb4338a.conf

- name: Build Bluetooth samples
working-directory: zephyr-silabs
shell: bash
run: |
west twister -v --inline-logs -K \
-s sample.bluetooth.peripheral_hr \
-s sample.bluetooth.observer \
-p xg27_dk2602a \
-p siwx917_rb4338a
Copy link
Collaborator

Choose a reason for hiding this comment

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

Wouldn't we still want to keep some amount of 917 testing here, just like we do for EFR32?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Probably yes.

Comment on lines 13 to 22
# Additional roots for boards and DTS files. Zephyr will use the
# `<board_root>/boards` for additional boards. The `.` is the root of this
# repository.
board_root: .
# Zephyr will use the `<dts_root>/dts` for additional dts files and
# `<dts_root>/dts/bindings` for additional dts binding files. The `.` is
# the root of this repository.
dts_root: .
# Zephyr will use the `<soc_root>/soc` for additional socs. The `.` is the
# root of this repository.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I'd consider keeping these, so that it remains possible to have boards in this tree in the future. Downstream (to us) users might also want to populate a fork of this tree with their own board definitions possibly (though, a better solution might be to have a separate manifest tree in that case that just points at this one)

west.yml Outdated
revision: a36c91b4cc49b9b54030121004a1565d6fc69475
revision: pull/85144/head
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why not just update this to the latest upstream main branch, since the PR was already merged?

Copy link
Collaborator

Choose a reason for hiding this comment

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

I think you should likely also start pointing at the upstream hal_silabs tree, i.e. remove the reference to the downstream one (which will eventually be removed completely)

Copy link
Collaborator

Choose a reason for hiding this comment

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

Why not just update this to the latest upstream main branch, since the PR was already merged?

I see you created this before the upstream PR was merged, which explains the reference. But now it can be updated to point at a real commit.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think you should likely also start pointing at the upstream hal_silabs tree

Ideally yes, but for now:

zephyr/modules/hal/silabs$ git diff --stat upstream/main silabs/silabs
[...]
 113 files changed, 49889 insertions(+), 5172 deletions(-)

(the differences mainly come from mbedtls/psa).

Copy link
Collaborator

Choose a reason for hiding this comment

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

Oh, I didn't realize we had that in our downstream tree. That needs to be sorted out first then, i.e. in the short term rebase our hal_silabs on upstream and in the long term upstream any changes, so that we can proceed with the "remove public downstream hal_silabs" plan.

@jerome-pouiller jerome-pouiller force-pushed the align-with-upstream branch 7 times, most recently from 7585d6a to d247962 Compare February 12, 2025 18:36
@jerome-pouiller jerome-pouiller marked this pull request as ready for review February 12, 2025 19:00
@jerome-pouiller jerome-pouiller requested a review from a team as a code owner February 12, 2025 19:00
jhedberg
jhedberg previously approved these changes Feb 12, 2025
dts/Kconfig Outdated
Copy link
Contributor

Choose a reason for hiding this comment

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

Why add a Kconfig file in dts? If you just want to keep the directory around, .gitignore would make more sense, since Kconfig will never be needed in the dts directory.

Copy link
Contributor

Choose a reason for hiding this comment

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

Same for this one.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This one was a mistake.

@jerome-pouiller
Copy link
Contributor Author

Revert to the draft state since hal_silabs miss some commits to allow compilation of 917.

@jerome-pouiller jerome-pouiller force-pushed the align-with-upstream branch 3 times, most recently from 831e19f to 49b9a5b Compare February 13, 2025 14:54
@jerome-pouiller
Copy link
Contributor Author

v2:

  • Place the workaround for check_compliance.py in a separated commit.
  • Do not drop test in build.yml. For now, we need to ensure this PR compile.
  • Update pointer for hal_silabs.

@jerome-pouiller jerome-pouiller marked this pull request as ready for review February 13, 2025 15:10
west.yml Outdated
path: modules/hal/silabs
- name: zephyr-mbedtls
remote: silabs
revision: 6024c415bf050c09e3990bddb6d53d3b4990a2b1
path: modules/crypto/mbedtls
- name: zephyr
remote: zephyrproject-rtos
revision: a36c91b4cc49b9b54030121004a1565d6fc69475
revision: f63c6113dedb6e31d968aa0bd239c009fa8b8a8e
Copy link
Collaborator

Choose a reason for hiding this comment

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

$ git log --pretty=oneline f63c6113dedb6e31d968aa0bd239c009fa8b8a8e..|wc -l
     188

Would be nice to update to a slightly newer upstream.

Upstream now include support for 917. So, we can drop it from the
downstream. We can also drop the tests related to the 917.

Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
Since commit f8a5ebfd2, check_compliance.py run "git grep CONFIG_" in
boards/ and soc/ directories. This command will fail if no match is
found. This failure prevent check_compliance.py to run properly.

The workaround is to add the word "CONFIG_BOARD" (any existing config
option will work) in a random file in boards/ and soc/

Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
Several things are easier now.

Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
@jerome-pouiller jerome-pouiller merged commit 67ab4b1 into SiliconLabsSoftware:main Feb 13, 2025
3 checks passed
@jerome-pouiller jerome-pouiller deleted the align-with-upstream branch February 18, 2025 12:18
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.

3 participants