Reminder: Zephyr Project: APIs When: 09/14/2021 4:00pm to 5:00pm (UTC+00:00) UTC Where: Microsoft Teams Meeting Organizer: devel@... An RSVP is requested. Click here to

Hello, Hmm... It seems that in CONFIG_USE_SWITCH=n case (ex. aarch32(*)) _current_cpu.current is updated by software interrupt handler. (*) arch/arm/core/aarch32/swap_helper.S So I wonder that why

Hello, I can check it directly. I think this is future work to achieve more faster switching than now. At this point, I want to implement most conservative one.. Best Regards, Katsuhiro Suzuki

Hi all, Agenda for today: - Pinctrl: Side-by-side comparison of two (similar) approaches proposed - PR #1: https://github.com/zephyrproject-rtos/zephyr/pull/37572 - PR #2:

Reminder: Zephyr Memory Footprint - biweekly discussion When: 09/13/2021 3:00pm to 4:00pm (UTC+00:00) UTC Where: Microsoft Teams Meeting Organizer: devel@... An RSVP is requested. Click

Here are the minutes from our last meeting:https://docs.google.com/document/d/1bnQLJKVhgI3zkk3MsSXun8onEsA8z1Rf5ohdbCHASmU/edit# I don’t have any agenda items for today. As we discussed last

Hi all, Today during a Discord conversation a user mentioned that support for the HX711 is currently in Pull Request form, but progress has stalled. I glanced through the PR and it seems to me that

Hi Markus, Do you have the include at the top of the driver you're developing which incluces the spi-device.yaml file, e.g. from one of the other LIS2XX devices: include: ["spi-device.yaml",

i'm facing a problem when i building the external_lib sample > west build -b nrf52dk_nrf52832 [1/142] Performing build step for 'mylib_project' FAILED:

Minutes: https://docs.google.com/document/d/15KUINNj7Re0GQiWYpqKvO5jgDw8oiQv3SGJfNHGaPOU/edit#heading=h.g794p090kv26

Alright, so thanks to Nick (thank you!) I have now narrowed down my problem a little. as a background, here is the C code that is causing the issue (i marked the error-origin in fat

Hi All, We're building a custom board with a no-standard power sequence. The processor and a TCA6418 GPIO expander come up first on a low-current 1V8 supply. The TCA6418 controls the enable pins for

hi i'm facing a problem when i building the external_lib sample > west build -b nrf52dk_nrf52832 [1/142] Performing build step for 'mylib_project' FAILED:

Reminder: Zephyr Project: Dev Meeting When: 09/09/2021 3:00pm to 4:00pm (UTC+00:00) UTC Where: Microsoft Teams Meeting Organizer: devel@... An RSVP is requested. Click here to

Hi, <katsuhiro@...> wrote: The reason why we set _current to the new thread is that we can't set it after we switch to the new thread. The newly switched thread will just start running

PINCTRL: - devicetree description (option 1 vs option 3) Option1 (grouping by device): NRF: https://gist.github.com/gmarull/e2afed5c97a188f3830ff0bd59d3d3ae NXP:

Can't you just check that flag in the context switch code?  It seems like that would be faster on average (most DSP workloads try very hard to avoid doing synchronous context switches to avoid the

Hello, Thanks for your advice. Current RISC-V implementation (CONFIG_USE_SWITCH=n) is using 'ecall' (this is SW interrupt instruction) to execute context switching explicitly. And jump into

Hello, Thank you for reply. Currently, No. I'm trying to add a support for CONFIG_USE_SWITCH=y case. Sorry for confusing. Older means CONFIG_USE_SWITCH=n. Does not means Zephyr's

Hi, <katsuhiro@...> wrote: Does RISC-V support USE_SWITCH? AFAICS, even with v1.11, we are setting `_current` to `new_thread` in `_Swap()` before calling `_arch_switch()`. What version are