Hi Erwan

I've taken another look at Christer Weinigel's patched for USB on STM32F4 recently.

I'm having a problem with the new LL clock code.

I applied the following patch to Christer's work in order to bring it up to date w.r.t. the LL clock driver:

diff --git a/drivers/usb/device/usb_dc_stm.c b/drivers/usb/device/usb_dc_stm.c
index 070e6766bf67..49f7dbffd5c3 100644
--- a/drivers/usb/device/usb_dc_stm.c
+++ b/drivers/usb/device/usb_dc_stm.c
@@ -149,9 +149,9 @@ static void usb_dc_stm_isr(void *arg)
 static int usb_dc_stm_clock_enable(void)
 {
        struct device *clk = device_get_binding(STM32_CLOCK_CONTROL_NAME);
-       struct stm32f4x_pclken pclken = {
-               .bus = STM32F4X_CLOCK_BUS_AHB2,
-               .enr = STM32F4X_CLOCK_ENABLE_OTGFS,
+       struct stm32_pclken pclken = {
+               .bus = STM32_CLOCK_BUS_AHB2,
+               .enr = LL_AHB2_GRP1_PERIPH_OTGFS,
        };

        clock_control_on(clk, (clock_control_subsys_t *)&pclken);

Unfortunately this change is not enough to get the USB code to work. Have I done the translation correctly?

I think the problem is one of enable rather than USB clock rate (there is no attempt to hotplug... if the USB clock rate were wrong hotplug detect would work but there would be no comms).

Finally, just to double check my assumptions about, I did do a bisect to try and chase thise problem down. bisect took me straight to 80b7bec ("soc: stm32f4: Enable LL based clock control") so I know this is strictly related to the clock driver change rather than any other zephyr changes.

Can you offer any clues?


Daniel.