Hi Felipe, On Mon, Jan 14, 2013 at 1:27 PM, Felipe Balbi <balbi@xxxxxx> wrote: > On Fri, Jan 11, 2013 at 07:58:23PM +0530, Vivek Gautam wrote: >> Hi, >> >> >> On Fri, Jan 11, 2013 at 7:29 PM, Felipe Balbi <balbi@xxxxxx> wrote: >> > Hi, >> > >> > On Fri, Jan 11, 2013 at 07:13:55PM +0530, Vivek Gautam wrote: >> >> On Thu, Jan 10, 2013 at 6:32 PM, Felipe Balbi <balbi@xxxxxx> wrote: >> >> > Hi, >> >> > >> >> > On Mon, Dec 24, 2012 at 07:28:33PM +0530, Vivek Gautam wrote: >> >> >> DWC3 controller curretly depends on CONFIG_USB and CONFIG_USB_GADGET. >> >> >> Some hardware may like to use only host feature on dwc3. >> >> >> So, removing the dependency of USB_DWC3 on USB_GADGET >> >> >> and further modulating the dwc3 core to enable gadget features >> >> >> only with USB_GADGET. >> >> >> >> >> >> Signed-off-by: Vivek Gautam <gautam.vivek@xxxxxxxxxxx> >> >> >> CC: Doug Anderson <dianders@xxxxxxxxxxxx> >> >> > >> >> > right, right... Eventually we need to do it, but you're only making >> >> > gadget side optional. Host side should be optional too, but then you >> >> > need to make sure we don't build dwc3 without gadget and host. >> >> > >> >> >> >> Yes, true we need to make host side also optional, build dwc3 only when >> >> either of host or gadget are built. >> > >> > btw, make the default Dual-Role, if user/defconfig doesn't select >> > anything we want to build with all features. >> > >> >> Yes we can try something like this ? >> >> if (USB || USB_GADGET) > > no need for this if, actually... > >> menuconfig USB_DWC3 >> tristate "DesignWare USB3 DRD Core Support" > > make it a "depends on (USB || USB_GAGDGET)" here > Yeah, sure. > other than that, it looks correct. Just make sure to compile test in all > options. > Yes ofcourse, i shall compile test all possible options. >> if USB_DWC3 >> choice >> default USB_DWC3_DUAL_ROLE_MODE >> ... >> >> config USB_DWC3_HOST_MODE > > this one should depend on USB > yes true. >> ... >> >> config USB_DWC3_DEVICE_MODE > > this one should depend on USB_GADGET > Ok, >> ... >> >> config USB_DWC3_DUAL_ROLE_MODE > > should depend on USB && USB_GADGET > Ok >> >> >> int dwc3_gadget_init(struct dwc3 *dwc); >> >> >> void dwc3_gadget_exit(struct dwc3 *dwc); >> >> >> +#else >> >> >> +static inline int dwc3_gadget_init(struct dwc3 *dwc) >> >> >> +{ return -EINVAL; } >> >> >> +static inline void dwc3_gadget_exit(struct dwc3 *dwc) >> >> >> +{ } >> >> >> +#endif >> >> >> >> >> >> #endif /* __DRIVERS_USB_DWC3_CORE_H */ >> >> >> diff --git a/drivers/usb/dwc3/debugfs.c b/drivers/usb/dwc3/debugfs.c >> >> >> index d4a30f1..553bbaa 100644 >> >> >> --- a/drivers/usb/dwc3/debugfs.c >> >> >> +++ b/drivers/usb/dwc3/debugfs.c >> >> >> @@ -535,7 +535,8 @@ static ssize_t dwc3_testmode_write(struct file *file, >> >> >> testmode = 0; >> >> >> >> >> >> spin_lock_irqsave(&dwc->lock, flags); >> >> >> - dwc3_gadget_set_test_mode(dwc, testmode); >> >> >> + if (dwc3_gadget_set_test_mode(dwc, testmode)) >> >> >> + dev_dbg(dwc->dev, "host: Invalid request\n"); >> >> >> spin_unlock_irqrestore(&dwc->lock, flags); >> >> >> >> >> >> return count; >> >> > >> >> > wrong, if you don't have gadget mode, you just don't create this file. >> >> > >> >> >> >> dwc3-core makes call to dwc3_debugfs_init() invariably depending on DEBUG_FS. >> >> Will this not go ahead and create this file ? >> >> I think i am missing here something. :-( >> > >> > right, you can change dwc3_debugfs_init() to take into account the fact >> > that you're a gadget/drd or host-only. >> > >> > In case of host only, you stil want regdump to be available :-) >> > >> >> So in dwc3_debugfs_init() we shall actually create just 'regdump' file >> in case of host only mode, otherwise keep the dwc3_debugfs_init() happy >> with creating other files too. >> Right ? > > right. > Ok so we shall change dwc3_debugfs_init(). Thanks for reviewing and suggesting changes. -- Thanks & Regards Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html