On Sunday 29 July 2007, Nikita V. Youshchenko wrote: > Hello people. > > Currently (as of 2.6.23-rc1), there are two definition of USB_OTG in > Kconfig files - one is in drivers/usb/core/Kconfig, and second is in > drivers/usb/gadget/Kconfig (and there, inside a choice). > > Is this double-definition a bug, or normal? > In the later case, maybe at least move second definition out of choice? > > Current situation is causing Kconfig warnings when playing around it (i.e. > add Kconfig support for more otg hardware), and I'm a bit confused on how > to deal with it.
It never used to complain. :) The basic situation is that OTG capability is something the whole stack -- both host and peripheral/gadget side -- needs to agree on. Plus, OTG must not be enabled if support for only one side is present; and there are cases where both sides will be present but it'd be wrong to enable OTG support. (Various development boards work that way, as do some embedded boards using USB to communicate between components.) So maybe what's needed is to just #define OTG as a boolean without a prompt, and then "select OTG" given some other Kconfig selection. That other Kconfig selection should probably live in the peripheral menu. - Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
