Previously a device which attempted to wake a sleeping host would not be
notified about the resumed operation and thus stay suspended for ever.

This is due to the fact that only a host initiated wakeup would trigger
a interrupt. As a workaround we use the SOF interrupt which is enabled
for a short amount of time to detect the resume of the bus and wakeup
the device.

Leftover Sonix reference code cleanup. Sometimes when there is traffic
on more than 1 ep's packets would be dropped before they could be handled.
Clearing the status flags after handling them takes care of it.

SN32: USB wakeup and interrupt handling cleanup

SN32: update registry

The former speed calculation where way off the requested i2c speeds.
This fix, which is based on the official pico-sdk implementation fixes
the calculation for the high and low times:

 | Speed | Before | After |
 | ------| ------ | ----- |
 | 100k  | 126k   | 94k   |
 | 400k  | 660k   | 346k  |
 | 1000k | - (*)  | 760k  |

(*) Failed to start any transaction in my test setup.

This fixes the USB endpoint get status functions; previously the
(wrong) assumptions were the following:

* `active` was toggled depending on whether a transaction was currently
  ongoing on the endpoint e.g., if the endpoint is "busy." What is  
  actually requested is if this endpoint is enabled at all. Therefore,
  we check the `enabled` flag in the endpoint control register.
* `stalled` was toggled by the device itself, although this property is
  completely controlled by the host via the SET and CLEAR feature
  requests. Therefore, we check the `stalled` flag in the endpoint
  buffer control register.

…-request

[RP2040] usb: fix usb_lld_get_status functions

[RP2040] i2c: fix speed calculation