|
Event: Zephyr Project: APIs - 09/14/2021
#cal-reminder
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
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
|
By
devel@lists.zephyrproject.org Calendar <noreply@...>
·
#8038
·
|
|
Re: Why do_swap() sets cpu.current before context switch?
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,
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
|
By
Katsuhiro Suzuki
·
#8037
·
|
|
Re: Why do_swap() sets cpu.current before context switch?
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
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
|
By
Katsuhiro Suzuki
·
#8036
·
|
|
API meeting: agenda
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:
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:
|
By
Carles Cufi
·
#8035
·
|
|
Event: Zephyr Memory Footprint - biweekly discussion - 09/13/2021
#cal-reminder
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
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
|
By
devel@lists.zephyrproject.org Calendar <noreply@...>
·
#8034
·
|
|
Re: Event: Zephyr Memory Footprint - biweekly discussion - 08/30/2021
#cal-reminder
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
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
|
By
Rob Woolley
·
#8033
·
|
|
HX711 support
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 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
|
By
Carles Cufi
·
#8032
·
|
|
Re: Unknown origin of error
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",
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",
|
By
lairdjm
·
#8031
·
|
|
a Problem with external_lib sample
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:
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:
|
By
Omar Morceli
·
#8030
·
|
|
Re: Dev-Review Meeting Agenda Sept 9th
Minutes: https://docs.google.com/document/d/15KUINNj7Re0GQiWYpqKvO5jgDw8oiQv3SGJfNHGaPOU/edit#heading=h.g794p090kv26
Minutes: https://docs.google.com/document/d/15KUINNj7Re0GQiWYpqKvO5jgDw8oiQv3SGJfNHGaPOU/edit#heading=h.g794p090kv26
|
By
Bolivar, Marti
·
#8029
·
|
|
Re: Unknown origin of error
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
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
|
By
markus.prager@...
·
#8028
·
|
|
Power sequencing and driver intialisation
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 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
|
By
Glenn Andrews
·
#8027
·
|
|
Problem when building external_lib sample
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:
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:
|
By
Omar Morceli
·
#8026
·
|
|
Event: Zephyr Project: Dev Meeting - 09/09/2021
#cal-reminder
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
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
|
By
devel@lists.zephyrproject.org Calendar <noreply@...>
·
#8025
·
|
|
Re: Why do_swap() sets cpu.current before context switch?
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
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
|
By
Yasushi SHOJI
·
#8024
·
|
|
Dev-Review Meeting Agenda Sept 9th
PINCTRL:
- devicetree description (option 1 vs option 3)
Option1 (grouping by device):
NRF: https://gist.github.com/gmarull/e2afed5c97a188f3830ff0bd59d3d3ae
NXP:
PINCTRL:
- devicetree description (option 1 vs option 3)
Option1 (grouping by device):
NRF: https://gist.github.com/gmarull/e2afed5c97a188f3830ff0bd59d3d3ae
NXP:
|
By
Kumar Gala
·
#8023
·
|
|
Re: Why do_swap() sets cpu.current before context switch?
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
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
|
By
Andy Ross
·
#8022
·
|
|
Re: Why do_swap() sets cpu.current before context switch?
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,
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
|
By
Katsuhiro Suzuki
·
#8021
·
|
|
Re: Why do_swap() sets cpu.current before context switch?
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
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
|
By
Katsuhiro Suzuki
·
#8020
·
|
|
Re: Why do_swap() sets cpu.current before context switch?
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
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
|
By
Yasushi SHOJI
·
#8019
·
|