### Describe the bug
With the new Bidirectional Dshot PR that just went in, ser…ial telemetry is broken when bidirectional dshot is not enabled.
With Bidirectional Dshot enabled
```
nsh> dshot status
INFO [dshot] Outputs initialized: yes
INFO [dshot] Outputs used: 0xf
INFO [dshot] Outputs on: yes
dshot: cycle: 331129 events, 12975063us elapsed, 39.18us avg, min 26us max 110us 2.957us rms
INFO [mixer_module] Param prefix: PWM_MAIN
control latency: 331134 events, 80084223us elapsed, 241.85us avg, min 204us max 435us 7.656us rms
INFO [mixer_module] Switched to rate_ctrl work queue
Channel Configuration:
Channel 0: func: 104, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
Channel 1: func: 101, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
Channel 2: func: 102, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
Channel 3: func: 103, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
Channel 4: func: 0, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
Channel 5: func: 0, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
Channel 6: func: 0, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
Channel 7: func: 0, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
Channel 8: func: 0, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
INFO [dshot] telemetry on: /dev/ttyS3
INFO [dshot] Number of successful ESC frames: 165254
INFO [dshot] Number of timeouts: 24
INFO [dshot] Number of CRC errors: 0
INFO [arch_dshot] dshot driver stats:
INFO [arch_dshot] Bidirectional DShot enabled
INFO [arch_dshot] Available DMA: 3
INFO [arch_dshot] Round robin enabled
INFO [arch_dshot] Timer 0, Channel 0: read 243309, failed nibble 2063, failed CRC 2595, invalid/zero 418
INFO [arch_dshot] Timer 0, Channel 1: read 242046, failed nibble 1615, failed CRC 3916, invalid/zero 811
INFO [arch_dshot] Timer 0, Channel 2: read 243363, failed nibble 1238, failed CRC 2619, invalid/zero 1169
INFO [arch_dshot] Timer 0, Channel 3: read 244497, failed nibble 531, failed CRC 2904, invalid/zero 461
nsh>
```
Without bidirectional dshot enabled. It looks like its just nor publishing to uorb.
```
nsh> dshot status
INFO [dshot] Outputs initialized: yes
INFO [dshot] Outputs used: 0xf
INFO [dshot] Outputs on: yes
dshot: cycle: 32015 events, 1127673us elapsed, 35.22us avg, min 25us max 124us 4.901us rms
INFO [mixer_module] Param prefix: PWM_MAIN
control latency: 32020 events, 6616053us elapsed, 206.62us avg, min 189us max 396us 6.539us rms
INFO [mixer_module] Switched to rate_ctrl work queue
Channel Configuration:
Channel 0: func: 104, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
Channel 1: func: 101, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
Channel 2: func: 102, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
Channel 3: func: 103, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
Channel 4: func: 0, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
Channel 5: func: 0, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
Channel 6: func: 0, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
Channel 7: func: 0, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
Channel 8: func: 0, value: 0, failsafe: 0, disarmed: 0, min: 109, max: 1999
INFO [dshot] telemetry on: /dev/ttyS3
INFO [dshot] Number of successful ESC frames: 15735
INFO [dshot] Number of timeouts: 21
INFO [dshot] Number of CRC errors: 0
nsh>
```