| Age | Commit message (Collapse) | Author |
|---|
|
This is a builtin fdt example BSP
Signed-off-by: GuEe-GUI <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
sampling windows.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- rt_console_output_enabled()/rt_console_output_is_enabled() gate rt_kprintf/rt_kputs output with the switch
|
|
* [components][clock_time] Refactor time subsystem around clock_time
Introduce the clock_time core with clock source/event separation, high-resolution scheduling, and boot-time helpers, plus clock_timer adapters for timer peripherals.
Remove legacy ktime/cputime/hwtimer implementations and migrate arch and BSP time paths to the new subsystem while keeping POSIX time integration functional.
Update drivers, Kconfig/SConscript wiring, documentation, and tests; add clock_time overview docs and align naming to clock_boottime/clock_hrtimer/clock_timer.
* [components][clock_time] Use BSP-provided clock timer frequency on riscv64
* [risc-v] Use runtime clock timer frequency for tick and delays
* [bsp] Add clock timer frequency hooks for riscv64 boards
* [bsp] Update Renesas RA driver doc clock_timer link
* [bsp] Sync zynqmp-r5-axu4ev rtconfig after config refresh
* [bsp][rk3500] Update rk3500 clock configuration
* [bsp][hpmicro] Add rt_hw_us_delay hook and update board delays
* [bsp][stm32l496-st-nucleo] enable clock_time for hwtimer sample in ci
* [bsp][hpmicro] Fix rtconfig include scope for hpm6750evk
Move rtconfig.h include outside the ENET_MULTIPLE_PORT guard for hpm6750evk and hpm6750evk2 so configuration macros are available regardless of ENET settings.
* [bsp][raspi3] select clock time for systimer
* [bsp][hpm5300evk] Trim trailing blank line
* [bsp][hpm5301evklite] Trim trailing blank line
* [bsp][hpm5e00evk] Trim trailing blank line
* [bsp][hpm6200evk] Trim trailing blank line
* [bsp][hpm6300evk] Trim trailing blank line
* [bsp][hpm6750evk] Trim trailing blank line
* [bsp][hpm6750evk2] Trim trailing blank line
* [bsp][hpm6750evkmini] Trim trailing blank line
* [bsp][hpm6800evk] Trim trailing blank line
* [bsp][hpm6e00evk] Trim trailing blank line
* [bsp][nxp] switch lpc178x to gcc and remove mcx timer source
* [bsp][stm32] fix the CONFIG_RT_USING_CLOCK_TIME issue.
* [docs][clock_time] add clock time documentation
* [docs][clock_time] Update clock time subsystem documentation
- Update device driver index to use correct page reference
- Clarify upper layer responsibilities in architecture overview
- Update README to describe POSIX/libc, Soft RTC, and device driver usage
- Refine architecture diagram with improved layout and color scheme
- Remove obsolete clock_timer.md file
* [kernel][utest] Trim trailing space
* [clock_time] Fix hrtimer wrap handling
* [clock_time] fix the static rt_inline issue
* [clock_time] fix the rt_clock_hrtimer_control result issue
|
|
|
|
|
|
as tracked in issue [#10895](https://github.com/RT-Thread/rt-thread/issues/10895). This leads to high maintenance costs, difficulty for new contributors, and inefficient code reviews.
Solution:
This patch adds the full, standardized documentation block to `sched_mtx_tc.c`, `sched_sem_tc.c`, `sched_thread_tc.c`, `sched_timed_mtx_tc.c` and `sched_timed_sem_tc.c` following the approved template.
The documentation details:
- Test Objectives and tested APIs
- Test Scenarios
- Verification Metrics
- Dependencies
- Test Execution command and Expected Results
This makes the test case's purpose and behavior immediately clear to future maintainers and reviewers.
Relates to [#10895](https://github.com/RT-Thread/rt-thread/issues/10895)
Signed-off-by: lhxj <[email protected]>
|
|
|
|
suspend repeatedly (#10970)
* Enhance thread suspend function with stricter checks
Refactor thread suspension logic to improve clarity and correctness.
* Clean up formatting in thread.c
Removed unnecessary blank line in thread.c.
* Refactor thread suspend state handling
Refactor thread suspension logic to improve clarity and maintainability.
* Update thread.c
* Fix indentation for RT_THREAD_SUSPEND_KILLABLE case
|
|
spinlock) #11011
|
|
Add comments for smp_thread_preemption.
Signed-off-by: Mengchen Teng <[email protected]>
|
|
Currently, the print information of this test case fails to demonstrate that
the high-priority thread has preempted the low-priority thread. This is because
when the high-priority thread prints the thread list, there is no information
about the low-priority thread (tlow), as tlow has already completed execution
and been destroyed. Therefore, the current execution logic cannot confirm the
successful completion of the preemption operation.
Solution: After the low-priority thread (tlow) releases the lock, add a busy-wait
loop while(!finish_flag);. At this point, when the high-priority thread (thigh)
prints the thread list information, tlow can be observed in the ready state, indicating
that it has been preempted by thigh.
Signed-off-by: Mengchen Teng <[email protected]>
|
|
In smp_assigned_idle_cores_tc, the finish_flag involves atomic operations
and thus requires address alignment.
Signed-off-by: Mengchen Teng <[email protected]>
|
|
Add comments for smp_bind_affinity, And fixed some comment issues in smp_affinity_pri2_tc.
Signed-off-by: Mengchen Teng <[email protected]>
|
|
Add comments for smp_affinity_pri2
Signed-off-by: Mengchen Teng <[email protected]>
|
|
Add comments for smp_affinity_pri1
Signed-off-by: Mengchen Teng <[email protected]>
|
|
Signed-off-by: ChuanN-sudo <[email protected]>
|
|
|
|
|
|
for idle harts
Add explanatory comments for the utest of smp_assigned_idle_cores.
Signed-off-by: Mengchen Teng <[email protected]>
|
|
Currently, this utest cannot determine whether threads are evenly distributed
across idle harts by observing the result of list_thread(). This is because
the presence of rt_thread_delay(5); causes all other threads to be in the
suspended state when thread information is printed. For example, if RT_CPUS_NR=4,
T0 executes list_thread() to print information, while T1~T3 are in hibernation
and thus it is impossible to observe which hart they are running on.
Solution:Here, the completion judgment condition has been modified. For example,
when RT_CPUS_NR=4, only RT_CPUS_NR-1 threads will be created (i.e., T0 to T2),
because running the utest occupies one hart. The execution is judged as completed
when finish_flag=0x0007, and the thread running the utest will call list_thread()
to print the information. Observe whether T0 to T2 are running on different
harts simultaneously.
Signed-off-by: Mengchen Teng <[email protected]>
|
|
truncation #10943
|
|
Signed-off-by: Ze-Hou <[email protected]>
|
|
Signed-off-by: Ze-Hou <[email protected]>
|
|
by improper priority configuration. (#10956)
|
|
by improper priority configuration.
|
|
mtsafe_kprint_tc #10945
|
|
|
|
Signed-off-by: Ze-Hou <[email protected]>
|
|
* [fix][utest] correct spelling of ''pref_test' to 'perf_test'
|
|
|
|
|
|
|
|
|
|
|
