You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by "Fix-Point (via GitHub)" <gi...@apache.org> on 2025/11/04 03:27:54 UTC
[PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Fix-Point opened a new pull request, #17276:
URL: https://github.com/apache/nuttx/pull/17276
## Summary
This PR proposed ClockDevice, a new timer driver abstraction for NuttX. The new CLOCKDEVICE timer hardware abstraction delivers:
- Functional correctness: Thread-safe and overflow-free
- High performance: Up to 3x faster on ARMv7A platforms
- Theoretically optimal timing precision: Uses hardware cycle counts as the time unit.
- Time-unit independent interfaces: Decouples timer drivers from OS time subsystems
- Minimalist driver implementation: Reduces driver code size by nearly 70%.
## Impact
These code commits affect the timing subsystem, as well as the following architecture:
- arm-v7a/arm-v7r/arm-v8r
- arm-v8a
- riscv
- sim
- tricore
- intel64.
## Testing
To evaluate the performance improvements, we conducted tests on three platforms: qemu-inte64/KVM, imx8qm-mek/arm64, and qemu-armv7a. We measured the CPU cycle overhead for:
- Reading the current time
- Setting a timer
- Handling a timer callback
Each operation was executed 10 million times, and the results were averaged.
The results demonstrated significant performance improvments.
On qemu-armv7a, the software division is the performance bottle-neck. ClockDevice bring significant performance improvements:
- clock_gettime 2.56x
- clock_systime_ticks 3.00x
- wd_start 1.67x
- wd_start_cancel 1.43x
- timer expiration 2.36x
<img width="579" height="435" alt="image" src="https://github.com/user-attachments/assets/dc7394c2-0cc8-4c99-81a8-2920f14fbc2b" />
On qemu-inte64/KVM, ClockDevice achieved up to 1.42x performance improved. Especially, for clock_gettime API, NuttX with ClockDevice improvements had 1.31x better performance than Linux Kernel 6.8.0-51.
<img width="597" height="448" alt="image" src="https://github.com/user-attachments/assets/5c3a2dba-5823-41f3-9e73-17f0327de25c" />
On imx8qm-mek/arm64, ClockDevice achieved up to 1.68x performance improvement. Note on the early ARM64 platform, the INVDIV optimization can not work well since the hardware division instruction UDIV costs less CPU cycles on average than the INVDIV.
<img width="607" height="455" alt="image" src="https://github.com/user-attachments/assets/576edd31-8a26-4a1c-8a5f-c86b8402157a" />
## Plan
Due to the need for extensive code modifications, some work remains unfinished. The following is a list of the planned tasks.
- [x] 1. Simplify the timer drivers and add SMP initialization.
- [x] 2. Remove the callback and arg from the oneshot API.
- [x] 3. Remove tick-based oneshot API.
- [x] 4. Add new count-based oneshot API (CLKDEV).
- [x] 5. Introduce optimized fast-path for count-based oneshot API.
- [x] 6. Reimplemented the common-use timer drivers with count-based oneshot API.
- [WIP] 7. Inlining arch_alarm for performance (3% ~ 5% less execution time for clock_gettime, wd_start and wd_expiration).
Architectures support:
- [x] arm-v7a/v7r/v8r generic timer
- [x] goldfish
- [x] arm-v8a generic timer
- [x] sim
- [x] intel64 tsc
- [x] tricore systimer
- [WIP/Soon] risc-v
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "Fix-Point (via GitHub)" <gi...@apache.org>.
Fix-Point commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3747306646
> > > @Fix-Point should we close this pr?
> >
> >
> > Please hold off on this, I will close this PR after the `8. Inlining arch_alarm for performance (3% ~ 5% less execution time for clock_gettime, wd_start and wd_expiration).` is finished and merged.
>
> @Fix-Point do we still need keep this pr?
Please keep this PR. I am sorry that this work is not yet complete since we have to modify the driver implementation. I will continue working on it once the hrtimer-related patches are merged.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "xiaoxiang781216 (via GitHub)" <gi...@apache.org>.
xiaoxiang781216 commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3525852574
> @xiaoxiang781216 @Fix-Point This looks similar to the hrtimer driver I planned to add in my PR #17065, which was intended to provide access to the hardware timer count.
>
> However, @xiaoxiang781216 mentioned in that PR that adding a new timer driver is not allowed in NuttX, so I removed the implementation, and reimplemented the sched/hrtimer based on the exsiting timer driver.
>
> Your PR to introcude ClockDevice makes me feel confused about the criteria for what kind of functionality is acceptable to add to NuttX...
This is still oneshot driver, but change the tick callback to count callback since the tick version lose the accuary of hardware timer, other major improvement include:
1. Provide the high efficient implementation of count<->tick and count<->timespec conversion in framework to simplify the driver developement.
2. Modify all arch general timer to utlize the new improvement, but still support the old interface
but this change doesn't add any new arch up_xxx function.
All above improvement isn't related to hrtimer at all, both tick and tickless mode can get the benifit(performance improvent and driver simplication) from this PR.
The new hrtimer implementation doesn't add any new arch up_xxx function too, which continue use up_(alarm|timer)_start/up_(alarm|timer)_cancel.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "tinnedkarma (via GitHub)" <gi...@apache.org>.
tinnedkarma commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3493702726
Hello all,
Maybe it's best if I wait for the documentation, but still.
There is already work done in drivers/clk, which defines clk_s and clk_ops_s, though I do not know anything more about them.
This ClockDevice seems to only talk about timers. Is there plan to also cover the work of drivers/clk? Or can we make it cover drivers/clk?
It's a bit confusing using ClockDevice name without relating to drivers/clk.
Thanks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "anchao (via GitHub)" <gi...@apache.org>.
anchao commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3510027297
> > Please hold this PR and do not merge it easily. @Fix-Point Could you split this patch into multiple PRs:
> >
> > 1. Split the ONESHOT_COUNT core implementation
> > 2. Split the division optimization
> > 3. Split the implementation for each architecture
> > 4. Split the defconfig changes
> >
> > Before the defconfig update in phase 4, the new clock framework should not be enabled in the system. The ONESHOT_COUNT framework needs time to prove itself; each developer should decide for themselves whether to enable this feature.
>
> But we had to revert the tick-based interfaces, which would cause performance degradation on these platforms and incur the overhead of re-verification. Besides, I think the new ClockDevice drivers are more reliable than the original, since they have fixed many timer driver bugs. E.g, the tricore systimer will miss interrupt if the next count to be set has already expired.
The ticks loss issue can be fixed by the counter register, and it shouldn't be a serious problem unless more than 2 toggle cycles are involved. The new framework needs further evaluation; although it's more accurate, I'm concerned it might increase CPU load, especially on 32-bit systems
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "Fix-Point (via GitHub)" <gi...@apache.org>.
Fix-Point commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3514838324
> @Fix-Point please fix ci issue:
>
> ```
> ../nuttx/tools/checkpatch.sh -c -u -m -g 6088f6216b8fe8a7f2cc76742403f7147bb9f823..HEAD
> Missing git commit message
> Commit subject missing colon (e.g. 'subsystem: msg')
> Missing git commit message
> Commit subject missing colon (e.g. 'subsystem: msg')
> Missing git commit message
> Commit subject missing colon (e.g. 'subsystem: msg')
> Missing git commit message
> Missing git commit message
> Missing git commit message
> Missing git commit message
> Used config files:
> 1: .codespellrc
> Some checks failed. For contributing guidelines, see:
>
> reading sources... [100%] substitutions
>
>
> Warning, treated as error:
> /home/runner/work/nuttx/nuttx/Documentation/components/drivers/timers/oneshot/index.rst:14:Definition list ends without a blank line; unexpected unindent.
> make: *** [Makefile:48: html] Error 2
> Error: Process completed with exit code 2.
> ```
Done.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "acassis (via GitHub)" <gi...@apache.org>.
acassis commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3490759037
> > @Fix-Point nice work! Please create a Documentation/ explaining the idea of the ClockDevice driver abstraction, its APIs, simple usage example and the info you provided here in the Summary with those graphics
>
> Understood, I will add relevant documentation in next few weeks.
Right, let move it to draft to avoid someone merging it accidentally.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "xiaoxiang781216 (via GitHub)" <gi...@apache.org>.
xiaoxiang781216 commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3570391554
@Fix-Point should we close this pr?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "xiaoxiang781216 (via GitHub)" <gi...@apache.org>.
xiaoxiang781216 commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3511699532
> > > Please hold this PR and do not merge it easily. @Fix-Point Could you split this patch into multiple PRs:
> > >
> > > 1. Split the ONESHOT_COUNT core implementation
> > > 2. Split the division optimization
> > > 3. Split the implementation for each architecture
> > > 4. Split the defconfig changes
> > >
> > > Before the defconfig update in phase 4, the new clock framework should not be enabled in the system. The ONESHOT_COUNT framework needs time to prove itself; each developer should decide for themselves whether to enable this feature.
> >
> >
> > But we had to revert the tick-based interfaces, which would cause performance degradation on these platforms and incur the overhead of re-verification. Besides, I think the new ClockDevice drivers are more reliable than the original, since they have fixed many timer driver bugs. E.g, the tricore systimer will miss interrupt if the next count to be set has already expired.
>
> The ticks loss issue can be fixed by the counter register, and it shouldn't be a serious problem unless more than 2 toggle cycles are involved. The new framework needs further evaluation; although it's more accurate, I'm concerned it might increase CPU load, especially on 32-bit systems
tick unit impact up_?delay reported here: https://github.com/apache/nuttx/pull/17221
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "linguini1 (via GitHub)" <gi...@apache.org>.
linguini1 commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3487370618
Hi @Fix-Point, a few things:
1) Great work! I know there are a lot of people who are excited for this change, including myself. I plan to re-watch your workshop presentation soon to get a better understanding
2) As I think was mentioned, please include some extensive documentation about this new feature. How does it work, when should it be used, does it make any guarantees (big one is to not timeout before the actual duration has passed), etc. You can even link to your talk from the docs. It would be really helpful not only to new users but also for developers, as I see this is replacing a lot of other timer implementations (?)
3) This PR is 47 commits long right now (not sure if that's intentional). I think we should split some of this up into multiple PRs if possible (i.e. one to add the feature, another for replacing existing timer usage with the new feature, etc.).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "xiaoxiang781216 (via GitHub)" <gi...@apache.org>.
xiaoxiang781216 commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3511684897
@Fix-Point please fix ci issue:
```
../nuttx/tools/checkpatch.sh -c -u -m -g 6088f6216b8fe8a7f2cc76742403f7147bb9f823..HEAD
Missing git commit message
Commit subject missing colon (e.g. 'subsystem: msg')
Missing git commit message
Commit subject missing colon (e.g. 'subsystem: msg')
Missing git commit message
Commit subject missing colon (e.g. 'subsystem: msg')
Missing git commit message
Missing git commit message
Missing git commit message
Missing git commit message
Used config files:
1: .codespellrc
Some checks failed. For contributing guidelines, see:
reading sources... [100%] substitutions
Warning, treated as error:
/home/runner/work/nuttx/nuttx/Documentation/components/drivers/timers/oneshot/index.rst:14:Definition list ends without a blank line; unexpected unindent.
make: *** [Makefile:48: html] Error 2
Error: Process completed with exit code 2.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "anchao (via GitHub)" <gi...@apache.org>.
anchao commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3494568398
Please hold this PR and do not merge it easily. @Fix-Point Could you split this patch into multiple PRs:
1. Split the ONESHOT_COUNT core implementation
2. Split the division optimization
3. Split the implementation for each architecture
4. Split the defconfig changes
Before the defconfig update in phase 4, the new clock framework should not be enabled in the system. The ONESHOT_COUNT framework needs time to prove itself; each developer should decide for themselves whether to enable this feature.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "xiaoxiang781216 (via GitHub)" <gi...@apache.org>.
xiaoxiang781216 closed pull request #17276: driver/timers: ClockDevice, a new timer driver abstraction for NuttX.
URL: https://github.com/apache/nuttx/pull/17276
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "wangchdo (via GitHub)" <gi...@apache.org>.
wangchdo commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3524895082
@xiaoxiang781216 @Fix-Point This looks similar to the hrtimer driver I planned to add in my PR https://github.com/apache/nuttx/pull/17065, which was intended to provide access to the hardware timer count.
However, @xiaoxiang781216 mentioned in that PR that adding a new timer driver is not allowed in NuttX, so I removed the implementation, and reimplemented the sched/hrtimer based on the exsiting timer driver.
Your PR to introcude clockdevice makes me feel confused about the criteria for what kind of functionality is acceptable to add to NuttX...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "Fix-Point (via GitHub)" <gi...@apache.org>.
Fix-Point commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3509963944
> Please hold this PR and do not merge it easily. @Fix-Point Could you split this patch into multiple PRs:
>
> 1. Split the ONESHOT_COUNT core implementation
> 2. Split the division optimization
> 3. Split the implementation for each architecture
> 4. Split the defconfig changes
>
> Before the defconfig update in phase 4, the new clock framework should not be enabled in the system. The ONESHOT_COUNT framework needs time to prove itself; each developer should decide for themselves whether to enable this feature.
But we had to revert the tick-based interfaces, which would cause some platform performance degradation and incur the overhead of verification. Besides, I think the new ClockDevice drivers is more reliable than the original, since they have fixed many timer driver bugs. E.g, the tricore systimer will miss interrupt if the next count to be set has already expired.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "xiaoxiang781216 (via GitHub)" <gi...@apache.org>.
xiaoxiang781216 commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3744419843
> > @Fix-Point should we close this pr?
>
> Please hold off on this, I will close this PR after the `8. Inlining arch_alarm for performance (3% ~ 5% less execution time for clock_gettime, wd_start and wd_expiration).` is finished and merged.
@Fix-Point do we still need keep this pr?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "Fix-Point (via GitHub)" <gi...@apache.org>.
Fix-Point commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3570793097
> @Fix-Point should we close this pr?
Please hold off on this, I will close this PR after the `8. Inlining arch_alarm for performance (3% ~ 5% less execution time for clock_gettime, wd_start and wd_expiration).` is finished and merged.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "Fix-Point (via GitHub)" <gi...@apache.org>.
Fix-Point commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3509940647
> > > @Fix-Point nice work! Please create a Documentation/ explaining the idea of the ClockDevice driver abstraction, its APIs, simple usage example and the info you provided here in the Summary with those graphics
> >
> >
> > Understood, I will add relevant documentation in next few weeks.
>
> Right, let move it to draft to avoid someone merging it accidentally.
The document has been added. Please check if it is appropriate or needs further refinement.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "xiaoxiang781216 (via GitHub)" <gi...@apache.org>.
xiaoxiang781216 commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3494437129
> Hello all,
>
> Maybe it's best if I wait for the documentation, but still. There is already work done in drivers/clk, which defines clk_s and clk_ops_s, though I do not know anything more about them. This ClockDevice seems to only talk about timers. Is there plan to also cover the work of drivers/clk? Or can we make it cover drivers/clk? It's a bit confusing using ClockDevice name without relating to drivers/clk.
>
> Thanks.
it's different subsystem:
- drivers/clk is for changing your peripheral(uart, spi, even timer) working clock frequency/phase etc.
- drivers/timer is for getting the current timestamp and trigger callback on the specific interval.
since clk subsystem design principle is same as Linux counterpart, so you can learn from Linux doc too:
https://docs.kernel.org/driver-api/clk.html
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "Fix-Point (via GitHub)" <gi...@apache.org>.
Fix-Point commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3488857877
> @Fix-Point nice work! Please create a Documentation/ explaining the idea of the ClockDevice driver abstraction, its APIs, simple usage example and the info you provided here in the Summary with those graphics
Understood, I will add relevant documentation in next few weeks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] driver/timers: ClockDevice, a new timer driver abstraction for NuttX. [nuttx]
Posted by "simbit18 (via GitHub)" <gi...@apache.org>.
simbit18 commented on PR #17276:
URL: https://github.com/apache/nuttx/pull/17276#issuecomment-3485566344
Hi @Fix-Point , bcm2711_timer.c is still present in Make.defs and CMakefile but has been removed.
https://github.com/Fix-Point/nuttx/blob/2dc2a345949e6f50830de48422b74a1fec92d473/arch/arm64/src/bcm2711/CMakeLists.txt#L24
https://github.com/Fix-Point/nuttx/blob/2dc2a345949e6f50830de48422b74a1fec92d473/arch/arm64/src/bcm2711/Make.defs#L29
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org