Currently the dwc2 driver only supports a single clock. I have a board here which has a dwc2 controller with a somewhat special clock routing to the phy. Both the dwc2 controller and the ULPI phy get their phy clock from a SI5351 clock generator. This clock generator has multiple clock outputs which each is modelled as a separate clk in Linux. Unfortunately the clock to the phy and the clock to the dwc2 core are on two different output pins of the SI5351, so we have two clocks which must be enabled. The phy is driven by the usb-nop-xceiver driver which supports a single clock. My first approach was to add support for a second clock to that driver, but technically the other clock is connected to the dwc2 core, so instead I added support for a second clock to the dwc2 driver. This can easily be archieved with the clk bulk API as done in this series. Changes since v1: - Add minItems to dec2 clock/clock-names property to avoid dt_binding_check warning Sascha Hauer (2): dt-bindings: usb: dwc2: Add support for additional clock usb: dwc2: use clk bulk API for supporting additional clocks .../devicetree/bindings/usb/dwc2.yaml | 5 ++++- drivers/usb/dwc2/core.h | 2 ++ drivers/usb/dwc2/platform.c | 18 ++++++++---------- 3 files changed, 14 insertions(+), 11 deletions(-) -- 2.20.1