Hi Kishon, On Wed, Apr 5, 2017 at 4:30 PM, Kishon Vijay Abraham I <kishon@xxxxxx> wrote: > Hi, > > On Tuesday 28 March 2017 05:57 PM, Raviteja Garimella wrote: >> This is driver for USB DRD Phy used in Broadcom's Northstar2 >> SoC. The phy can be configured to be in Device mode or Host >> mode based on the type of cable connected to the port. The >> driver registers to extcon framework to get appropriate >> connect events for Host/Device cables connect/disconnect >> states based on VBUS and ID interrupts. > > $patch should be phy: phy-bcm-ns2-usbdrd: USB DRD Phy driver for Broadcoms > Northstar2. > Will do. > Sorry for not letting you know this earlier. But I feel the design of the > driver should be changed. Extcon shouldn't be used here. The extcon > notifications should be sent to the consumer driver and the consumer driver > should be responsible for invoking the phy ops. > The consumer drivers here would be a UDC driver (USB device controller), EHCI and OHCI host controller drivers. I was already suggested in UDC driver review to deal with extcon in Phy driver. This phy connects to 2 host controllers, and one device controller. That's the design in Broadcom Northstar2 platform. The values of the VBUS and ID pins of this port are determined based on the type of the cable (device cable or host cable). And. phy has to be configured accordingly. > The phy ops being invoked during extcon events doesn't look right. Could you please elaborate on the concern, so that we can think of mitigating those issues in this driver? Since we are dealing with phy init/shutdown in this driver itself, are you okay with moving the extcon handling code out of phy ops ? Thanks, Ravi > > Thanks > Kishon -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
