Skip to content

Add support for RX architecture CI on Zephyr #91769

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

Merged
merged 33 commits into from
Jun 26, 2025

Conversation

duynguyenxa
Copy link
Member

@duynguyenxa duynguyenxa commented Jun 17, 2025

This PR is a continued work on the #89770 to fix all RX architecture qemu environment to enable CI test for it.
These fixes will also need to apply change in the qemu source code, fix patch is updated at: zephyrproject-rtos/sdk-ng#944

@duynguyenxa
Copy link
Member Author

duynguyenxa commented Jun 17, 2025

Current result execute on local with qemu-target-rx fix:

529 of 573 executed test configurations passed (92.32%), 24 built (not run), 11 failed, 0 errored, with 1 warnings in 721.10 seconds.

There are 6 failure cases seem to be issue with twister harness cannot send input command to qemu.
Others are still under checking


ERROR   - qemu_rx/r5f562n8          samples/sensor/sensor_shell/sample.sensor.shell.pytest FAILED: 5/5 pytest scenario(s) failed
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/sensor/sensor_shell/sample.sensor.shell.pytest/twister_harness.log
ERROR   - qemu_rx/r5f562n8          samples/basic/hash_map/sample.libraries.hash_map.newlib.cxx_unordered_map.djb2 FAILED: unexpected eof
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/basic/hash_map/sample.libraries.hash_map.newlib.cxx_unordered_map.djb2/build.log
ERROR   - qemu_rx/r5f562n8          samples/subsys/shell/shell_module/sample.shell.shell_module FAILED: 1/1 pytest scenario(s) failed
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/subsys/shell/shell_module/sample.shell.shell_module/twister_harness.log
ERROR   - qemu_rx/r5f562n8          samples/subsys/testsuite/pytest/shell/sample.harness.shell.vt100_colors_off FAILED: 1/1 pytest scenario(s) failed
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/subsys/testsuite/pytest/shell/sample.harness.shell.vt100_colors_off/twister_harness.log
ERROR   - qemu_rx/r5f562n8          samples/subsys/testsuite/pytest/shell/sample.harness.shell FAILED: 1/1 pytest scenario(s) failed
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/subsys/testsuite/pytest/shell/sample.harness.shell/twister_harness.log
ERROR   - qemu_rx/r5f562n8          samples/subsys/testsuite/pytest/shell/sample.pytest.shell FAILED: 2/2 pytest scenario(s) failed
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/subsys/testsuite/pytest/shell/sample.pytest.shell/twister_harness.log
ERROR   - qemu_rx/r5f562n8          samples/subsys/testsuite/pytest/shell/sample.pytest.shell.vt100_colors_off FAILED: 2/2 pytest scenario(s) failed
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/subsys/testsuite/pytest/shell/sample.pytest.shell.vt100_colors_off/twister_harness.log
ERROR   - qemu_rx/r5f562n8          tests/lib/hash_map/libraries.hash_map.cxx.djb2     FAILED: unexpected eof
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/tests/lib/hash_map/libraries.hash_map.cxx.djb2/build.log
ERROR   - qemu_rx/r5f562n8          tests/lib/cpp/libcxx/cpp.libcxx.glibcxx.picolibc   FAILED: unexpected eof
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/tests/lib/cpp/libcxx/cpp.libcxx.glibcxx.picolibc/build.log
ERROR   - qemu_rx/r5f562n8          tests/lib/cpp/libcxx/cpp.libcxx.glibcxx.newlib     FAILED: unexpected eof
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/tests/lib/cpp/libcxx/cpp.libcxx.glibcxx.newlib/build.log
WARNING - A None status detected in instance qemu_rx/r5f562n8/zephyr/tests/subsys/fs/lib_link/filesystem.lib_link, test case filesystem.lib_link.
ERROR   - qemu_rx/r5f562n8          tests/subsys/zbus/integration/message_bus.zbus.module_interaction_no_error FAILED: Testsuite failed
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/tests/subsys/zbus/integration/message_bus.zbus.module_interaction_no_error/handler.log
INFO    - Total complete:  777/ 777  100%  built (not run):   24, filtered: 2946, failed:   11, error:    0
INFO    - 3741 test scenarios (3519 configurations) selected, 2946 configurations filtered (2742 by static filter, 204 at runtime).
INFO    - 529 of 573 executed test configurations passed (92.32%), 24 built (not run), 11 failed, 0 errored, with 1 warnings in 721.10 seconds.
INFO    - 4527 of 4566 executed test cases passed (99.15%), 25 blocked, 13 failed, 1 without a status on 1 out of total 1088 platforms (0.09%).
INFO    - 624 selected test cases not executed: 588 skipped, 36 not run (built only).
INFO    - 540 test configurations executed on platforms, 15 test configurations were only built.
INFO    - Saving reports...
INFO    - Writing JSON report /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/twister.json
INFO    - Writing xunit report /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/twister.xml...
INFO    - Writing xunit report /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/twister_report.xml...

@nashif
Copy link
Member

nashif commented Jun 17, 2025

Hmm, there are many commits here that are not qemu/rx related, those require the 0.18 SDK version and some of them are obsolete, please keep this series focused on the qemu changes and drop anything that is unrelated and general SDK changes.

@@ -9,7 +9,15 @@ simulation:
arch: rx
toolchain:
- cross-compile
- zephyr
- zephyr-gnu
Copy link
Member

Choose a reason for hiding this comment

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

zephyr-gnu is not needed and is not used anymore in the sdk, just drop it for now.

@nashif
Copy link
Member

nashif commented Jun 18, 2025

tried with patched qemu, looks good, the following fail for me, some could be relatedto my setup, i.e. nanopb:

INFO    - Adding tasks to the queue...
INFO    - Added initial list of jobs to queue
INFO    -   1/577 qemu_rx/r5f562n8          sample.modules.nanopb                              ERROR Build failure (qemu <zephyr>)
ERROR   - see: /home/nashif/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/modules/nanopb/sample.modules.nanopb/build.log
INFO    -   2/577 qemu_rx/r5f562n8          libraries.nanopb                                   ERROR Build failure (qemu <zephyr>)
ERROR   - see: /home/nashif/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/tests/modules/nanopb/libraries.nanopb/build.log
INFO    -   3/577 qemu_rx/r5f562n8          message_bus.zbus.module_interaction_no_error       FAILED Testsuite failed (qemu 4.262s <zephyr>)
ERROR   - see: /home/nashif/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/tests/subsys/zbus/integration/message_bus.zbus.module_interaction_no_error/handler.log
INFO    -   4/577 qemu_rx/r5f562n8          sample.harness.shell                               FAILED 1/1 pytest scenario(s) failed (qemu 1.879s <zephyr>)
ERROR   - see: /home/nashif/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/subsys/testsuite/pytest/shell/sample.harness.shell/twister_harness.log
INFO    -   5/577 qemu_rx/r5f562n8          sample.shell.shell_module                          FAILED 1/1 pytest scenario(s) failed (qemu 1.879s <zephyr>)
ERROR   - see: /home/nashif/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/subsys/shell/shell_module/sample.shell.shell_module/twister_harness.log
INFO    -   6/577 qemu_rx/r5f562n8          sample.harness.shell.vt100_colors_off              FAILED 1/1 pytest scenario(s) failed (qemu 1.771s <zephyr>)
ERROR   - see: /home/nashif/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/subsys/testsuite/pytest/shell/sample.harness.shell.vt100_colors_off/twister_harness.log
INFO    -   7/577 qemu_rx/r5f562n8          sample.pytest.shell.vt100_colors_off               FAILED 2/2 pytest scenario(s) failed (qemu 3.698s <zephyr>)
ERROR   - see: /home/nashif/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/subsys/testsuite/pytest/shell/sample.pytest.shell.vt100_colors_off/twister_harness.log
INFO    -   8/577 qemu_rx/r5f562n8          sample.pytest.shell                                FAILED 2/2 pytest scenario(s) failed (qemu 3.788s <zephyr>)
ERROR   - see: /home/nashif/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/subsys/testsuite/pytest/shell/sample.pytest.shell/twister_harness.log
INFO    -   9/577 qemu_rx/r5f562n8          sample.sensor.shell.pytest                         FAILED 5/5 pytest scenario(s) failed (qemu 9.191s <zephyr>)
ERROR   - see: /home/nashif/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/sensor/sensor_shell/sample.sensor.shell.pytest/twister_harness.log
INFO    -  10/577 qemu_rx/r5f562n8          sample.libraries.hash_map.newlib.cxx_unordered_map.djb2 FAILED unexpected eof (qemu 12.409s <zephyr>)
ERROR   - see: /home/nashif/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/basic/hash_map/sample.libraries.hash_map.newlib.cxx_unordered_map.djb2/build.log
INFO    -  11/577 qemu_rx/r5f562n8          cpp.libcxx.glibcxx.picolibc                        FAILED unexpected eof (qemu 12.110s <zephyr>)
ERROR   - see: /home/nashif/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/tests/lib/cpp/libcxx/cpp.libcxx.glibcxx.picolibc/build.log
INFO    -  12/577 qemu_rx/r5f562n8          cpp.libcxx.glibcxx.newlib                          FAILED unexpected eof (qemu 14.787s <zephyr>)
ERROR   - see: /home/nashif/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/tests/lib/cpp/libcxx/cpp.libcxx.glibcxx.newlib/build.log
INFO    -  13/577 qemu_rx/r5f562n8          libraries.hash_map.cxx.djb2                        FAILED unexpected eof (qemu 12.493s <zephyr>)
ERROR   - see: /home/nashif/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/tests/lib/hash_map/libraries.hash_map.cxx.djb2/build.log

shell stuff probably fails because of lack of UART features? anyways, those are samples and probably can be excluded for now, others in lib/cpp probably need some attention.

@duynguyenxa
Copy link
Member Author

duynguyenxa commented Jun 20, 2025

shell stuff probably fails because of lack of UART features? anyways, those are samples and probably can be excluded for now, others in lib/cpp probably need some attention.

I'm not sure what happen with the twister harness, it seem that the harness script cannot input command to qemu console, I run each test case manually by using "west build -t run" and I can interact with the shell just fine.

There is issue with objcopy in the libcxx test, somehow it's running wrong with the gapfill and generate a 4GB bin file.
The format for RX target is .mot on actual HW so I submitting patch to workaround the issue by loading the elf format to qemu platform with the new patch on zephyrproject-rtos/sdk-ng#945

Current status (failed: 8, error: 0), aside the shell stuff there are 2 remaining fails:
tests/lib/cpp/libcxx/cpp.libcxx.glibcxx.newlib
tests/subsys/zbus/integration/message_bus.zbus.module_interaction_no_error

ERROR   - qemu_rx/r5f562n8          samples/sensor/sensor_shell/sample.sensor.shell.pytest FAILED: 5/5 pytest scenario(s) failed
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/sensor/sensor_shell/sample.sensor.shell.pytest/twister_harness.log
ERROR   - qemu_rx/r5f562n8          samples/subsys/shell/shell_module/sample.shell.shell_module FAILED: 1/1 pytest scenario(s) failed
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/subsys/shell/shell_module/sample.shell.shell_module/twister_harness.log
ERROR   - qemu_rx/r5f562n8          samples/subsys/testsuite/pytest/shell/sample.harness.shell.vt100_colors_off FAILED: 1/1 pytest scenario(s) failed
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/subsys/testsuite/pytest/shell/sample.harness.shell.vt100_colors_off/twister_harness.log
ERROR   - qemu_rx/r5f562n8          samples/subsys/testsuite/pytest/shell/sample.harness.shell FAILED: 1/1 pytest scenario(s) failed
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/subsys/testsuite/pytest/shell/sample.harness.shell/twister_harness.log
ERROR   - qemu_rx/r5f562n8          samples/subsys/testsuite/pytest/shell/sample.pytest.shell.vt100_colors_off FAILED: 2/2 pytest scenario(s) failed
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/subsys/testsuite/pytest/shell/sample.pytest.shell.vt100_colors_off/twister_harness.log
ERROR   - qemu_rx/r5f562n8          samples/subsys/testsuite/pytest/shell/sample.pytest.shell FAILED: 2/2 pytest scenario(s) failed
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/samples/subsys/testsuite/pytest/shell/sample.pytest.shell/twister_harness.log
ERROR   - qemu_rx/r5f562n8          tests/lib/cpp/libcxx/cpp.libcxx.glibcxx.newlib     FAILED: unexpected byte
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/tests/lib/cpp/libcxx/cpp.libcxx.glibcxx.newlib/handler.log
WARNING - A None status detected in instance qemu_rx/r5f562n8/zephyr/tests/subsys/fs/lib_link/filesystem.lib_link, test case filesystem.lib_link.
ERROR   - qemu_rx/r5f562n8          tests/subsys/zbus/integration/message_bus.zbus.module_interaction_no_error FAILED: Testsuite failed
ERROR   - see: /home/duyhoangnguyen/zephyrproject/zephyr/twister-out/qemu_rx_r5f562n8/zephyr/tests/subsys/zbus/integration/message_bus.zbus.module_interaction_no_error/handler.log
INFO    - Total complete:  776/ 776  100%  built (not run):   24, filtered: 2945, failed:    8, error:    0
INFO    - 3740 test scenarios (3518 configurations) selected, 2945 configurations filtered (2742 by static filter, 203 at runtime).
INFO    - 532 of 573 executed test configurations passed (92.84%), 24 built (not run), 8 failed, 0 errored, with 1 warnings in 710.88 seconds.

@duynguyenxa
Copy link
Member Author

Update: Incorrect define of SRAM size in dts of qemu_rx make tests/lib/cpp/libcxx/cpp.libcxx.glibcxx.newlib due to not enough RAM, I updated to correct size, now test case is passed.
Remaining 6 failed due to twister harness and 1 unknown reason failed case: tests/subsys/zbus/integration/message_bus.zbus.module_interaction_no_error

@duynguyenxa
Copy link
Member Author

Hello @nashif , @keith-packard , @kartben , Can you please help to take a look, all test are passed on my local with the qemu patched, currently I'm skipping the shell sample, I created #92003 to keep track for it and will add it later

INFO    - Total complete:  770/ 770  100%  built (not run):   24, filtered: 2951, failed:    0, error:    0
INFO    - 3740 test scenarios (3518 configurations) selected, 2951 configurations filtered (2748 by static filter, 203 at runtime).
INFO    - 539 of 567 executed test configurations passed (95.06%), 24 built (not run), 0 failed, 0 errored, with 1 warnings in 658.63 seconds.
INFO    - 4607 of 4608 executed test cases passed (99.98%), 1 without a status on 1 out of total 1088 platforms (0.09%).
INFO    - 570 selected test cases not executed: 534 skipped, 36 not run (built only).
INFO    - 539 test configurations executed on platforms, 20 test configurations were only built.

@nashif
Copy link
Member

nashif commented Jun 25, 2025

@duynguyenxa there is something wrong with this PR, qemu_rx builds are not working at all, i.e.. not even hello world is running for me.

@nashif
Copy link
Member

nashif commented Jun 25, 2025

I verified with old qemu and new qemu on an older commit in main, and it seems to work.
currently qemu_rx builds in main are failing with some DTS errors.

@duynguyenxa
Copy link
Member Author

duynguyenxa commented Jun 25, 2025

I verified with old qemu and new qemu on an older commit in main, and it seems to work. currently qemu_rx builds in main are failing with some DTS errors.

@nashif , yes it's due to #89555 merge change the binding of ICU node of RX
fix is provide at f2fca08 in this PR. Sorry, should've finished this first before the other PR merge

@nashif
Copy link
Member

nashif commented Jun 25, 2025

@nashif , yes it's due to #89555 merge change the binding of ICU node of RX fix is provide at f2fca08 in this PR. Sorry, should've finished this first before the other PR merge

ok, but still when it builds now, it does not run at all in qemu.

@duynguyenxa
Copy link
Member Author

duynguyenxa commented Jun 25, 2025

@nashif , sorry this is my mistake, I'm adding the 00019 patch but forget to put it in the .bb file, the qemu in Zephyr SDK is missing 1 patch
https://github.com/zephyrproject-rtos/sdk-ng/blob/v0.17-branch/meta-zephyr-sdk/recipes-devtools/qemu/qemu-zephyr_10.0.2.bb

@nashif
Copy link
Member

nashif commented Jun 25, 2025

@nashif , sorry this is my mistake, I'm adding the 00019 patch but forget to put it in the .bb file, the qemu in Zephyr SDK is missing 1 patch
zephyrproject-rtos/sdk-ng@v0.17-branch/meta-zephyr-sdk/recipes-devtools/qemu/qemu-zephyr_10.0.2.bb

ok, partly also my mistake, should have caught that. Any way we can work around this, the offending commit right now is 8ddb13d, can we try and get at least the basic testing with qemu_rx working without the need for another SDK release?

@duynguyenxa
Copy link
Member Author

yes we can, Only need to drop 8ddb13d and c85e12b in this PR, but we have to add exclude for some cases because of bad bin generate by objcopy.

@nashif
Copy link
Member

nashif commented Jun 25, 2025

yes we can, Only need to drop 8ddb13d and c85e12b in this PR, but we have to add exclude for some cases because of bad bin generate by objcopy.

Ok, maybe remove those 2 commits for now and do the following in the board yaml file:

testing:
  default: true
  only_tags:
     - kernel
  ignore_tags:
    - net
    - bluetooth
    - can

and get this going, you can later remove this and fine tune filtering.

The RX QEMU platform SRAM size is 96KB, this commit correct the
device tree information

Signed-off-by: Duy Nguyen <duy.nguyen.xa@renesas.com>
Somehow icount shift making this test fail on qemu_rx target
maybe clock rate on RX is too low, as work around I disable
the icount shift for this test case on qemu_rx

Signed-off-by: Duy Nguyen <duy.nguyen.xa@renesas.com>
The qemu_rx is having issue with twister harness, command cannot
be send from twister test to qemu console, this commit temporary
disable them for further checking

Signed-off-by: Duy Nguyen <duy.nguyen.xa@renesas.com>
The qemu_rx some how with too big offset in "mov" instruction
cannot manipulate the memory correctly
This commit reconfigure the slot count to reduce the size of
psa_global_data_t struct so that issue on qemu_rx not occur

Signed-off-by: Duy Nguyen <duy.nguyen.xa@renesas.com>
Add zephyr toolchain support to rsk_rx130 board

Signed-off-by: Duy Nguyen <duy.nguyen.xa@renesas.com>
Update interrupt controller node to be compatible with new
binding configuration

Signed-off-by: Duy Nguyen <duy.nguyen.xa@renesas.com>
Adding rx-zephyr-elf for testing rx target

Signed-off-by: Duy Nguyen <duy.nguyen.xa@renesas.com>
Ignore gapfill for RX target as some RX toolchains generate wrong
output image when running gapfill for binary format.

Signed-off-by: Duy Nguyen <duy.nguyen.xa@renesas.com>
@duynguyenxa
Copy link
Member Author

yes we can, Only need to drop 8ddb13d and c85e12b in this PR, but we have to add exclude for some cases because of bad bin generate by objcopy.

Ok, maybe remove those 2 commits for now and do the following in the board yaml file:

testing:
  default: true
  only_tags:
     - kernel
  ignore_tags:
    - net
    - bluetooth
    - can

and get this going, you can later remove this and fine tune filtering.

I drop the 2 commits, and disable the gap_fill option on RX target for now

Board device tree is missing ioport3 status set okay for
button. Add missing ioport3 enable

Signed-off-by: Duy Nguyen <duy.nguyen.xa@renesas.com>
@nashif
Copy link
Member

nashif commented Jun 25, 2025

one failing test is due to #92187

@duynguyenxa
Copy link
Member Author

one failing test is due to #92187

I checked the other on my local but it's Passed without changing anything, now not sure how I can solve this.

image

@nashif
Copy link
Member

nashif commented Jun 25, 2025

I checked the other on my local but it's Passed without changing anything, now not sure how I can solve this.

yeah, not sure. I also cant reproduce this locally. I would open a bug and exclude this test referencing the bug for now while we figure things out.,

Excluding this test for qemu_rx because it's failing randomly
Root cause not identified yet, zephyrproject-rtos#92213 is created to keep track
of this
This test case is working fine on actual RX HW so issue might be
in the inside the qemu environment

Signed-off-by: Duy Nguyen <duy.nguyen.xa@renesas.com>
From Zephyr SDK 0.17.1 the RX architecture is supported so
update the documentation of RX130 board to reflect this

Signed-off-by: Duy Nguyen <duy.nguyen.xa@renesas.com>
@duynguyenxa
Copy link
Member Author

It seem that after a few time re-attempt the job pass, it's passing inconsistently.
I verified the test case on actual HW the RSK-RX130 many time and there are no issue, maybe there is issue in qemu environment, anyway I created the #92213 to track it, hopefully can resolve it soon
In this PR I exclude the test case kernel.workqueue.api for qemu RX

Copy link

@kartben kartben merged commit 5465fc3 into zephyrproject-rtos:main Jun 26, 2025
56 of 58 checks passed
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.

6 participants