summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* usb: dwc3: core: explicitly setup and cleanup event buffersFelipe Balbi2013-03-181-15/+17
| | | | | | | | | Make the call to dwc3_event_buffers_setup() and dwc3_event_buffers_cleanup() explicit, so it's easier to implement PM. Tested-by: Vivek Gautam <gautam.vivek@samsung.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: mv_udc_core: switch over to usb_gadget_map/unmap_request()Felipe Balbi2013-03-181-47/+6
| | | | | | | we have generic implementations for a reason, let's use them Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: lpc32xx_udc: switch over to usb_gadget_map/unmap_request()Felipe Balbi2013-03-181-35/+4
| | | | | | | we have generic implementations for a reason, let's use them Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: fusb300: switch over to usb_gadget_map/unmap_request()Felipe Balbi2013-03-181-10/+7
| | | | | | | we have generic implementations for a reason, let's use them Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: fsl_udc_core: switch over to usb_gadget_map/unmap_request()Felipe Balbi2013-03-181-38/+13
| | | | | | | we have generic implementations for a reason, let's use them Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: atmel_usba_udc: switch over to usb_gadget_map/unmap_request()Felipe Balbi2013-03-181-21/+6
| | | | | | | we have generic implementations for a reason, let's use them. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: amd5536udc: remove unused structure memberFelipe Balbi2013-03-181-1/+0
| | | | | | | that member isn't used anywhere in the driver and be removed with no mercy. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: s3c-hsotg: switch over to usb_gadget_map/unmap_request()Felipe Balbi2013-03-181-41/+5
| | | | | | | we have generic implementations for a reason, let's use them. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: drop now unnecessary flagFelipe Balbi2013-03-1830-43/+7
| | | | | | | | | | We don't need the ->register_my_device flag anymore because all UDC drivers have been properly converted. Let's remove every history of it. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: chipidea: let udc-core manage gadget->devFelipe Balbi2013-03-181-11/+2
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: pxa27x_udc: let udc-core manage gadget->devFelipe Balbi2013-03-181-11/+1
| | | | | | | | By simply setting a flag, we can drop some boilerplate code. Acked-by: Robert Jarzmik <robert.jarzmik@free.fr> Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: pxa25x_udc: let udc-core manage gadget->devFelipe Balbi2013-03-181-11/+1
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: renesas_usbhs: gadget: let udc-core manage gadget->devFelipe Balbi2013-03-181-9/+2
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: s3c2410_udc: let udc-core manage gadget->devFelipe Balbi2013-03-181-11/+1
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: s3c-hsudc: let udc-core manage gadget->devFelipe Balbi2013-03-181-10/+1
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: s3c-hsotg: let udc-core manage gadget->devFelipe Balbi2013-03-181-13/+1
| | | | | | | | By simply setting a flag, we can drop some boilerplate code. Reviewed-by: Tomasz Figa <tomasz.figa@gmail.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: r8a66597-udc: let udc-core manage gadget->devFelipe Balbi2013-03-181-10/+2
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: pch_udc: let udc-core manage gadget->devFelipe Balbi2013-03-181-9/+1
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: net2280: let udc-core manage gadget->devFelipe Balbi2013-03-181-4/+1
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: net2272: let udc-core manage gadget->devFelipe Balbi2013-03-181-8/+2
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: mv_udc_core: let udc-core manage gadget->devFelipe Balbi2013-03-181-10/+2
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: mv_u3d_core: fix a compile warningFelipe Balbi2013-03-181-1/+1
| | | | | | | | | Fix the following compile warning: mv_u3d_core.c:1766:12: warning: 'mv_u3d_remove' \ defined but not used [-Wunused-function] Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: mv_u3d_core: let udc-core manage gadget->devFelipe Balbi2013-03-181-9/+1
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: m66592-udc: let udc-core manage gadget->devFelipe Balbi2013-03-181-12/+1
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: lpc32xx_udc: let udc-core manage gadget->devFelipe Balbi2013-03-181-10/+1
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: imx_udc: let udc-core manage gadget->devFelipe Balbi2013-03-181-10/+2
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: goku_udc: let udc-core manage gadget->devFelipe Balbi2013-03-182-11/+2
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: fusb300_udc: let udc-core manage gadget->devFelipe Balbi2013-03-181-13/+1
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: fsl_udc_core: let udc-core manage gadget->devFelipe Balbi2013-03-181-7/+2
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: fsl_qe_udc: let udc-core manage gadget->devFelipe Balbi2013-03-181-13/+2
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: dummy_hcd: let udc-core manage gadget->devFelipe Balbi2013-03-181-9/+1
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: bcm63xx_udc: let udc-core manage gadget->devFelipe Balbi2013-03-181-7/+1
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: atmel_usba_udc: let udc-core manage gadget->devFelipe Balbi2013-03-181-12/+1
| | | | | | | By simply setting a flag, we can drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: at91_udc: let udc-core manage gadget->devFelipe Balbi2013-03-181-11/+2
| | | | | | | By simply setting a flag, we can remove some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: amd5536udc: let udc-core manage gadget->devFelipe Balbi2013-03-181-8/+1
| | | | | | | By simply setting a flag, we drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: omap_udc: let udc-core manage gadget->devFelipe Balbi2013-03-181-8/+4
| | | | | | | By simply setting a flag, we drop some boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: musb: gadget: let udc-core manage gadget-devFelipe Balbi2013-03-181-9/+1
| | | | | | | By simply setting a flag, we can delete a little boilerplate code. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: dwc3: gadget: let udc-core manage gadget->devFelipe Balbi2013-03-181-15/+2
| | | | | | | We don't need to register that device ourselves if we simply set gadget->register_my_device. Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: gadget: udc-core: allow udc class register gadget deviceFelipe Balbi2013-03-182-4/+23
| | | | | | | | | | | | | | | | | | | | | Currently all UDC drivers are calling device_register() before calling usb_add_gadget_udc(). In order to avoid code duplication, we can allow udc-core.c register that device. However that would become a really large patch, so to cope with the meanwhile and allow us to write bite-sized patches, we're adding a flag which will be set by UDC driver once it removes the code for registering the gadget device. Once all are converted, the new flag will be removed. Reviewed-by: Tomasz Figa <tomasz.figa@gmail.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: dwc3: omap: stop using nop-usb-xceivKishon Vijay Abraham I2013-03-181-67/+0
| | | | | | | | Now that we have drivers for omap-usb2 phy and omap-usb3 phy, stop using nop-usb-xceiv. Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: dwc3: omap: remove platform data associated with dwc3-omapKishon Vijay Abraham I2013-03-182-18/+10
| | | | | | | | omap5 is not going to have support for non-dt boot making the platform data associated with dwc3 useless. Removed it here. Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: dwc3: omap: minor fixes to get dt workingKishon Vijay Abraham I2013-03-182-24/+49
| | | | | | | | | | | | | | | | | Includes few minor fixes in dwc3-omap like populating the compatible string in a correct way, extracting the utmi-mode property properly and changing the index of get_irq since irq of core is removed from hwmod entry. Also updated the documentation with dwc3-omap device tree binding information. Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com> [ balbi@ti.com : fix a compile warning introduced by this commit ] Signed-off-by: Felipe Balbi <balbi@ti.com>
* USB: phy: nop: Defer probe if device needs VCC/RESETRoger Quadros2013-03-181-0/+11
| | | | | | | | | | | | | | | | | Add 2 flags, needs_vcc and needs_reset to platform data. If the flag is set and the regulator couldn't be found then we bail out with -EPROBE_DEFER. For device tree boot we depend on presensce of vcc-supply/ reset-supply properties to decide if we should bail out with -EPROBE_DEFER or just continue in case the regulator can't be found. This is required for proper functionality in cases where the regulator is needed but is probed later than the PHY device. Signed-off-by: Roger Quadros <rogerq@ti.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: phy: nop: Add device tree support and binding informationRoger Quadros2013-03-182-8/+61
| | | | | | | | The PHY clock, clock rate, VCC regulator and RESET regulator can now be provided via device tree. Signed-off-by: Roger Quadros <rogerq@ti.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: phy: nop: use new PHY API to register PHYRoger Quadros2013-03-181-1/+2
| | | | | | | | We would need to support multiple PHYs of the same type so use the new PHY API usb_add_phy_dev() to register the PHY. Signed-off-by: Roger Quadros <rogerq@ti.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: phy: nop: Handle RESET for the PHYRoger Quadros2013-03-181-0/+19
| | | | | | | | | | | | | We expect the RESET line to be modeled as a regulator with supply name "reset". The regulator should be modeled such that enabling the regulator brings the PHY device out of RESET and disabling the regulator holds the device in RESET. They PHY will be held in RESET in .shutdown() and brought out of RESET in .init(). Signed-off-by: Roger Quadros <rogerq@ti.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: phy: nop: Handle power supply regulator for the PHYRoger Quadros2013-03-181-0/+18
| | | | | | | | | We use "vcc" as the supply name for the PHY's power supply. The power supply will be enabled during .init() and disabled during .shutdown() Signed-off-by: Roger Quadros <rogerq@ti.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: phy: nop: Manage PHY clockRoger Quadros2013-03-181-1/+53
| | | | | | | | | | | If the PHY has a clock associated to it then manage the clock. We just enable the clock in .init() and disable it in .shutdown(). Add clk_rate parameter in platform data and configure the clock rate during probe if supplied. Signed-off-by: Roger Quadros <rogerq@ti.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: phy: nop: use devm_kzalloc()Roger Quadros2013-03-181-12/+5
| | | | | | | Use resource managed kzalloc. Signed-off-by: Roger Quadros <rogerq@ti.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
* usb: phy: nop: Add some parameters to platform dataRoger Quadros2013-03-181-0/+5
| | | | | | | | | | | | | Add clk_rate parameter to platform data. If supplied, the NOP phy driver will program the clock to that rate during probe. Also add 2 flags, needs_vcc and needs_reset. If the flag is set and the regulator couldn't be found then the driver will bail out with -EPROBE_DEFER. Signed-off-by: Roger Quadros <rogerq@ti.com> Acked-by: Felipe Balbi <balbi@ti.com> Signed-off-by: Felipe Balbi <balbi@ti.com>
OpenPOWER on IntegriCloud