Is usbd_edpt_claim() also intended to be used for the control endpoint?

[RockyZeroFour]

Is the function usbd_edpt_claim() for claiming an endpoint before sending data over it also intended to be used for the control endpoint?

To my understanding that function is only for the non-control endpoints. It's also only used in the driver. If I get it right, the control endpoint also has an independent handling which can be busy but not be claimed.

Right now any endpoint can be successfully claimed, the control endpoint as well as an unsupported endpoint. So a custom driver can access the _usbd_dev.ep_status out of bounce or the HID driver can claim the control endpoint when data is tried to send on an instance where no IN endpoint is assigned to.

[RockyZeroFour]

diff --git a/src/device/usbd.c b/src/device/usbd.c
index 99647c1..ec4e021 100644
--- a/src/device/usbd.c
+++ b/src/device/usbd.c
@@ -1280,6 +1280,9 @@ bool usbd_edpt_claim(uint8_t rhport, uint8_t ep_addr)
   // TU_VERIFY(tud_ready());
 
   uint8_t const epnum       = tu_edpt_number(ep_addr);
+
+  TU_ASSERT( 0 < epnum && CFG_TUD_ENDPPOINT_MAX > epnum );
+
   uint8_t const dir         = tu_edpt_dir(ep_addr);
   tu_edpt_state_t* ep_state = &_usbd_dev.ep_status[epnum][dir];