[BUG] Oneshot stopped working after #17339

[fdcavalcanti]

Description / Steps to reproduce the issue

Hi folks,

Noticed some changes on oneshot driver on #17339. It has caused the oneshot app to stop working on ESP32-C3.
I verified with git bisect and it works fine before the changes of that PR.

Here's how to reproduce with QEMU:

• ./tools/configure.sh esp32c3-generic:timers
• Enable CONFIG_ESPRESSIF_MERGE_BINS
• Run on QEMU or flash a devkit.
• For QEMU:

qemu-system-riscv32 -nographic -icount 3 -machine esp32c3 -m 4M \
            -drive file=nuttx.merged.bin,if=mtd,format=raw \
            -global driver=esp32c3.gpio,property=strap_mode,value=0x08 \
            -global driver=nvram.esp32c3.efuse,property=drive,value=efuse

• Execute the oneshot app:

nsh> oneshot
Opening /dev/oneshot
Maximum delay is 4294967295999999
Starting oneshot timer with delay 2000000 microseconds
Waiting...

It hangs at that point and does not return. It seems it calls the signal dispatch but nothing happens.

Appreciate the help in fixing this.

Thanks in advance,
Filipe

On which OS does this issue occur?

[OS: Linux]

What is the version of your OS?

Mint 22

NuttX Version

master

Issue Architecture

[Arch: risc-v]

Issue Area

[Area: Drivers]

Host information

No response

Verification

• I have verified before submitting the report.

[xiaoxiang781216]

@Fix-Point please look at this problem.

[Fix-Point]

My changes caused the oneshot callback to receive incorrect parameters.
The commit f9ea6fe in this PR #17345 should fix the issue.
Tested esp32c3-generic:timers on qemu-system-riscv32, ostest and examples/oneshot passed.