- 03 Nov, 2014 40 commits
-
-
Huang Rui authored
When parameter DWC_USB3_LPM_ERRATA_ENABLE is enabled in Andvanced Configuration of coreConsultant, it supports of xHCI BESL Errata Dated 10/19/2011 is enabled in host mode. In device mode it adds the capability to send NYET response threshold based on the BESL value received in the LPM token, and the threhold is configurable for each soc platform. This patch adds an entry that soc platform is able to define the lpm capacity with their own device tree or bus glue layer. [ balbi@ti.com : added devicetree documentation, spelled threshold completely, made sure threshold is only applied to proper core revisions. ] Signed-off-by:
Huang Rui <ray.huang@amd.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Huang Rui authored
This patch adds disscramble quirk, and it only needs to be enabled at fpga board on some vendor platforms. Signed-off-by:
Huang Rui <ray.huang@amd.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Huang Rui authored
This patch initializes platform data at pci glue layer, and SoCs x86-based platform vendor is able to define their flags in platform data at bus glue layer. Then do some independent behaviors at dwc3 core level. Signed-off-by:
Huang Rui <ray.huang@amd.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Huang Rui authored
Some chip vendor is on pre-silicon phase, which needs to use the simulation board. It should have the same product and vendor id with the true soc, but might have some minor different configurations. Below thread discussion proposes to find a method to distinguish between simulation board and soc. http://marc.info/?l=linux-usb&m=141194772206369&w=2 In Andvanced Configuration of coreConsultant, there is the parameter of DWC_USB_EN_FPGA. This bit has the function we need. And it would response as 7 bit of GHWPARAMS6 register. So it's able to check this functional bit to confirm if works on FPGA board. Reported-by:
Felipe Balbi <balbi@ti.com> Signed-off-by:
Huang Rui <ray.huang@amd.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Huang Rui authored
It enables hibernation if the function is set in coreConsultant. Suggested-by:
Felipe Balbi <balbi@ti.com> Signed-off-by:
Huang Rui <ray.huang@amd.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Antoine Tenart authored
This patch adds support of the PHY framework for ChipIdea drivers. Changes are done in both the ChipIdea common code and in the drivers accessing the PHY. This is done by adding a new PHY member in ChipIdea's structures and by taking care of it in the code. Signed-off-by:
Antoine Tenart <antoine.tenart@free-electrons.com> Acked-by:
Peter Chen <peter.chen@freescale.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Antoine Tenart authored
This patch modify the generic code handling PHYs to allow them to be supplied from the drivers. This adds checks to ensure no PHY was already there when looking for one in the generic code. This also makes sure we do not modify its state in the generic HCD functions, it was provided by the driver. Signed-off-by:
Antoine Tenart <antoine.tenart@free-electrons.com> Acked-by:
Alan Stern <stern@rowland.harvard.edu> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Antoine Tenart authored
This patch adds support of the PHY framework in OTG and keeps the USB PHY compatibility. Here the only modification is to add PHY member in the OTG structure, along with the USB PHY one. Signed-off-by:
Antoine Tenart <antoine.tenart@free-electrons.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Antoine Tenart authored
This patch prepares the introduction of the generic PHY support in the USB OTG common functions. The USB PHY member of the OTG structure is renamed to 'usb_phy' and modifications are done in all drivers accessing it. Renaming this pointer will allow to keep the compatibility for USB PHY drivers. Signed-off-by:
Antoine Tenart <antoine.tenart@free-electrons.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Antoine Tenart authored
Before using the PHY framework instead of the USB PHY one, we need to move the OTG state into another place, since it won't be available when USB PHY isn't used. This patch moves the OTG state into the OTG structure, and makes all the needed modifications in the drivers using the OTG state. [ balbi@ti.com : fix build regressions with phy-tahvo.c, musb_dsps.c, phy-isp1301-omap, and chipidea's debug.c ] Acked-by:
Kishon Vijay Abraham I <kishon@ti.com> Acked-by:
Peter Chen <peter.chen@freescale.com> Signed-off-by:
Antoine Tenart <antoine.tenart@free-electrons.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Fengguang Wu authored
drivers/usb/gadget/udc/r8a66597-udc.c:1849:1-3: WARNING: PTR_ERR_OR_ZERO can be used Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR Generated by: scripts/coccinelle/api/ptr_ret.cocci Signed-off-by:
Fengguang Wu <fengguang.wu@intel.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Pavitrakumar Managutte authored
Added failure check for usb_assign_descriptors call in bind function. Acked-By:
Sebastian Andrzej Siewior <bigeasy@linutronix.de> Signed-off-by:
Pavitrakumar Managutte <pavitra1729@gmail.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Sebastian Andrzej Siewior authored
In commit 0ec8fd70 ("USB: musb: fix possible panic while resuming") musb_resume() became musb_resume_early() in order to enable the clocks early on resume. This piece of the resume code was removed later in commit 03491761 ("usb: musb: move clock handling to glue layer"). In between the function was renamed from musb_resume_early() to musb_resume_noirq() by commit commit 48fea965 ("USB: Rework musb suspend()/resume_early()"). Now I see that first musb_core is resumed followed by phy and glue layer and I ask myself is this really what we intend to do? This kind of revoked the purpose of the first commit (0ec8fd70). Because of this and because it looks wrong to resume (core) before the glue layer I push it to the ->resume callback. Signed-off-by:
Sebastian Andrzej Siewior <bigeasy@linutronix.de> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Marek Szyprowski authored
This patch moves calls to phy enable/disable out of spinlock protected blocks in device suspend/resume to fix incorrect caller context. Phy related functions must not be called from atomic context. To protect device internal state from a race during suspend, a call to s3c_hsotg_core_disconnect() is added under a spinlock, what prevents any further activity on the usb bus. Acked-by:
Paul Zimmerman <paulz@synopsys.com> Signed-off-by:
Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Marek Szyprowski authored
This patch moves udc initialization from pullup() method to s3c_hsotg_udc_start(), so that method ends with hardware fully initialized and left in soft-disconnected state. After this change, the pullup() method simply clears soft-disconnect start() when called with is_on=1. For completeness, a call to s3c_hsotg_core_disconnect() has been added when pullup() method is called with is_on=0, what puts the udc hardware back to soft-disconnected state. Acked-by:
Paul Zimmerman <paulz@synopsys.com> Signed-off-by:
Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Marek Szyprowski authored
This patch moves phy enable/disable calls from pullup() method to udc_start/stop functions. This solves the issue related to limited caller context for PHY functions, because they cannot be called from non-sleeping context. This is also a preparation for using soft-disconnect feature of udc controller in pullup() method. Acked-by:
Paul Zimmerman <paulz@synopsys.com> Signed-off-by:
Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Marek Szyprowski authored
This patch changes s3c_hsotg_core_init function to leave hardware in soft disconnect mode, so the moment of coupling the hardware to the usb bus can be later controlled by the separate functions for enabling and disabling soft disconnect mode. This patch is a preparation to rework pullup() method. Acked-by:
Paul Zimmerman <paulz@synopsys.com> Signed-off-by:
Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Marek Szyprowski authored
This patch removes duplicated code and sets last_rst variable in the function which does the hardware reset. Acked-by:
Paul Zimmerman <paulz@synopsys.com> Signed-off-by:
Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Varka Bhadram authored
Sanity check on resource happening with devm_ioremap_resource(). Signed-off-by:
Varka Bhadram <varkab@cdac.in> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Varka Bhadram authored
Sanity check on resource happening with devm_ioremap_resource(). Signed-off-by:
Varka Bhadram <varkab@cdac.in> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Varka Bhadram authored
Sanity check on resource happening with devm_ioremap_resource(). Signed-off-by:
Varka Bhadram <varkab@cdac.in> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Varka Bhadram authored
Sanity check on resource happening with devm_ioremap_resource(). Signed-off-by:
Varka Bhadram <varkab@cdac.in> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Varka Bhadram authored
Sanity check on resource happening with devm_ioremap_resource(). Signed-off-by:
Varka Bhadram <varkab@cdac.in> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Sergei Shtylyov authored
The OMAP2+ MUSB glue layer still uses a bare number for the DEVCTL.B-Device bit in one place, while there's #define MUSB_DEVCTL_BDEVICE for that. Signed-off-by:
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Felipe Balbi authored
that call is completely unnecessary because usb_del_gadget_udc() already makes sure the gadget driver is properly unregistered from the UDC. Acked-by:
Robert Jarzmik <robert.jarzmik@free.fr> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Felipe Balbi authored
that call is completely unnecessary because usb_del_gadget_udc() already makes sure the gadget driver is properly unregistered from the UDC. Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Felipe Balbi authored
that call is completely unnecessary because usb_del_gadget_udc() already makes sure the gadget driver is properly unregistered from the UDC. Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Felipe Balbi authored
that call is completely unnecessary because usb_del_gadget_udc() already makes sure the gadget driver is properly unregistered from the UDC. Acked-by:
Paul Zimmerman <paulz@synopsys.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Robert Jarzmik authored
As the udc clock controls both the output signals and the internal IP, it must be enabled before any UDC register is touched. The bug is revealed when the clock framework disables the clock for a couple of milliseconds during the boot sequence, and the endpoint configuration is lost. The bug is hidden when clock framework is not used, because no "unused clocks disable" occurs. This patch fixes the wrong behaviour by ensuring that : - whenever a UDC register is read or written, the clock is enabled - reworks the endpoints programming to have it done under running clock - reworks suspend/resume to ensure the same thing Signed-off-by:
Robert Jarzmik <robert.jarzmik@free.fr> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Robert Jarzmik authored
Use devm_* helpers in the probe function to simplify the error path and the remove path. Signed-off-by:
Robert Jarzmik <robert.jarzmik@free.fr> Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Robert Jarzmik authored
Add documentation for device-tree binding of arm PXA 27x udc (usb device) driver. Signed-off-by:
Robert Jarzmik <robert.jarzmik@free.fr> Cc: devicetree@vger.kernel.org Acked-by:
Arnd Bergmann <arnd@arndb.de> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Felipe Balbi authored
No functional changes, just adding a prefix which should have been there from the start. Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Felipe Balbi authored
now that no UDC driver relies on the extra 'driver' argument to ->udc_stop(), we can safely remove it. This commit is based on previous work by Robert Baldyga <r.baldyga@samsung.com> which can be found at [1]; however that patch turned out to have a high probability of regressing many UDC drivers because of a blind search & replace s/driver/$udc->driver/ which caused the 'driver' argument to stop_activity() to be a valid non-NULL pointer when it should be NULL, thus causing UDCs to mistakenly call gadget driver's ->disconnect() callback. [1] http://markmail.org/message/x5zneg4xea4zntabAcked-by:
Peter Chen <peter.chen@freescale.com> Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Felipe Balbi authored
Currently, we're printing gadget driver name when registering and UDC name when unregistering. Standardize on always printing gadget driver name. Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Felipe Balbi authored
now that we provide generic register/unregister debugging messages from udc-core, we can remove the same messages from this driver. Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Felipe Balbi authored
now that we provide generic register/unregister debugging messages from udc-core, we can remove the same messages from this driver. Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Felipe Balbi authored
now that we provide generic register/unregister debugging messages from udc-core, we can remove the same messages from this driver. Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Felipe Balbi authored
now that we provide generic register/unregister debugging messages from udc-core, we can remove the same messages from this driver. Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Felipe Balbi authored
now that we provide generic register/unregister debugging messages from udc-core, we can remove the same messages from this driver. Signed-off-by:
Felipe Balbi <balbi@ti.com>
-
Felipe Balbi authored
now that we provide generic register/unregister debugging messages from udc-core, we can remove the same messages from this driver. Signed-off-by:
Felipe Balbi <balbi@ti.com>
-