Hi, Roger Quadros <[email protected]> writes: >> Roger Quadros <[email protected]> writes: >>>>> diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h >>>>> index 186a886..2e20892 100644 >>>>> --- a/drivers/usb/dwc3/core.h >>>>> +++ b/drivers/usb/dwc3/core.h >>>>> @@ -716,6 +716,8 @@ struct dwc3_scratchpad_array { >>>>> * @maximum_speed: maximum speed requested (mainly for testing purposes) >>>>> * @revision: revision register contents >>>>> * @dr_mode: requested mode of operation >>>>> + * @gadget_irq: IRQ number for Peripheral IRQs >>>>> + * @otg_irq: IRQ number for OTG IRQs >>>>> * @usb2_phy: pointer to USB2 PHY >>>>> * @usb3_phy: pointer to USB3 PHY >>>>> * @usb2_generic_phy: pointer to USB2 PHY >>>>> @@ -817,6 +819,9 @@ struct dwc3 { >>>>> >>>>> enum usb_dr_mode dr_mode; >>>>> >>>>> + int gadget_irq; >>>>> + int otg_irq; >>>> >>>> while at that, let's add host_irq too and do proper changes to dwc3/host.c >>> >>> Sure. So we add host_irq here, and manually create an irq resource >>> in dwc3_host_init? >> >> right :-) Then the code looks similar for otg, peripheral and host parts ;-) >> > Just saw that host_irq is not used anywhere other than creating the XHCI > platform > device. So I don't see why we need host_irq in struct dwc3. > It is obtained in dwc3_host_init() and consumed there itself.
fair enough. -- balbi
signature.asc
Description: PGP signature
