> > @@ -3,7 +3,7 @@ > > # > > obj-$(CONFIG_USB_PHY) += phy.o > > obj-$(CONFIG_OF) += of.o > > -obj-$(CONFIG_USB_OTG_FSM) += phy-fsm-usb.o > > +obj-$(CONFIG_USB_OTG) += phy-fsm-usb.o > > I'm not sure we should do this, what if people want to use the FSM as a > standalone library ? (we just got chipidea patches for that) > > Also, even if we don't have OTG support, we can still use parts of the > FSM and just ignore HNP and some other OTG-only details. > > --
This FSM is dedicated for HNP, and can't be used for partial otg support, like id role switch, and the CONFIG_USB_OTG will be selected if CONFIG_USB_OTG_FSM is chosen at current design. The only reason I think we need to keep CONFIG_USB_OTG_FSM is the usb 3.0 usb otg fsm may not back compatible with 2.0's, so we will have 3.0 fsm design. Peter -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
