Merge tag 'usb-for-v3.19' of git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-next

Felipe writes:

usb: patches for v3.19 merge window

This time, a very pull request with 216 non-merge
commits. Most of the commits contained here are
sparse or coccinelle fixes ranging from missing
'static' to returning 0 in case of errors.

More importantly, we have the removal the now
unnecessary 'driver' argument to ->udc_stop().

DWC2 learned about Dual-Role builds. Users of
this IP can now have a single driver built for
host and device roles.

DWC3 got support for two new HW platforms: Exynos7
and AMD.

The Broadcom USB 3.0 Device Controller IP is now
supported and so is PLX USB338x, which means DWC3
has lost is badge as the only USB 3.0 peripheral
IP supported on Linux.

Thanks for Tony Lindgren's work, we can now have
a distro-like kernel where all MUSB glue layers
can be built into the same kernel (statically
or dynamically linked) and it'll work in PIO (DMA
will come probably on v3.20).

Other than these, the usual set of cleanups and
non-critical fixes.

Signed-off-by: Felipe Balbi <balbi@ti.com>

7 files changed, 172 insertions, 2 deletions

diff --git a/Documentation/ABI/stable/sysfs-class-udc b/Documentation/ABI/stable/sysfs-class-udc
new file mode 100644
index 000000000000..85d3dac2e204
--- /dev/null
+++ b/Documentation/ABI/stable/sysfs-class-udc
@@ -0,0 +1,93 @@
+What:           /sys/class/udc/<udc>/a_alt_hnp_support
+Date:           June 2011
+KernelVersion:  3.1
+Contact:        Felipe Balbi <balbi@kernel.org>
+Description:
+                Indicates if an OTG A-Host supports HNP at an alternate port.
+Users:
+
+What:           /sys/class/udc/<udc>/a_hnp_support
+Date:           June 2011
+KernelVersion:  3.1
+Contact:        Felipe Balbi <balbi@kernel.org>
+Description:
+                Indicates if an OTG A-Host supports HNP at this port.
+Users:
+
+What:           /sys/class/udc/<udc>/b_hnp_enable
+Date:           June 2011
+KernelVersion:  3.1
+Contact:        Felipe Balbi <balbi@kernel.org>
+Description:
+                Indicates if an OTG A-Host enabled HNP support.
+Users:
+
+What:           /sys/class/udc/<udc>/current_speed
+Date:           June 2011
+KernelVersion:  3.1
+Contact:        Felipe Balbi <balbi@kernel.org>
+Description:
+                Indicates the current negotiated speed at this port.
+Users:
+
+What:           /sys/class/udc/<udc>/is_a_peripheral
+Date:           June 2011
+KernelVersion:  3.1
+Contact:        Felipe Balbi <balbi@kernel.org>
+Description:
+                Indicates that this port is the default Host on an OTG session
+                but HNP was used to switch roles.
+Users:
+
+What:           /sys/class/udc/<udc>/is_otg
+Date:           June 2011
+KernelVersion:  3.1
+Contact:        Felipe Balbi <balbi@kernel.org>
+Description:
+                Indicates that this port support OTG.
+Users:
+
+What:           /sys/class/udc/<udc>/maximum_speed
+Date:           June 2011
+KernelVersion:  3.1
+Contact:        Felipe Balbi <balbi@kernel.org>
+Description:
+                Indicates the maximum USB speed supported by this port.
+Users:
+
+What:           /sys/class/udc/<udc>/maximum_speed
+Date:           June 2011
+KernelVersion:  3.1
+Contact:        Felipe Balbi <balbi@kernel.org>
+Description:
+                Indicates the maximum USB speed supported by this port.
+Users:
+
+What:           /sys/class/udc/<udc>/soft_connect
+Date:           June 2011
+KernelVersion:  3.1
+Contact:        Felipe Balbi <balbi@kernel.org>
+Description:
+                Allows users to disconnect data pullup resistors thus causing a
+                logical disconnection from the USB Host.
+Users:
+
+What:           /sys/class/udc/<udc>/srp
+Date:           June 2011
+KernelVersion:  3.1
+Contact:        Felipe Balbi <balbi@kernel.org>
+Description:
+                Allows users to manually start Session Request Protocol.
+Users:
+
+What:           /sys/class/udc/<udc>/state
+Date:           June 2011
+KernelVersion:  3.1
+Contact:        Felipe Balbi <balbi@kernel.org>
+Description:
+                Indicates current state of the USB Device Controller. Valid
+                states are: 'not-attached', 'attached', 'powered',
+                'reconnecting', 'unauthenticated', 'default', 'addressed',
+                'configured', and 'suspended'; however not all USB Device
+                Controllers support reporting all states.
+Users:
diff --git a/Documentation/ABI/testing/configfs-usb-gadget-hid b/Documentation/ABI/testing/configfs-usb-gadget-hid
new file mode 100644
index 000000000000..f12e00e6baa3
--- /dev/null
+++ b/Documentation/ABI/testing/configfs-usb-gadget-hid
@@ -0,0 +1,11 @@
+What:           /config/usb-gadget/gadget/functions/hid.name
+Date:           Nov 2014
+KernelVersion:  3.19
+Description:
+                The attributes:
+
+                protocol        - HID protocol to use
+                report_desc     - blob corresponding to HID report descriptors
+                                except the data passed through /dev/hidg<N>
+                report_length   - HID report length
+                subclass        - HID device subclass to use
diff --git a/Documentation/ABI/testing/configfs-usb-gadget-midi b/Documentation/ABI/testing/configfs-usb-gadget-midi
new file mode 100644
index 000000000000..6b341df7249c
--- /dev/null
+++ b/Documentation/ABI/testing/configfs-usb-gadget-midi
@@ -0,0 +1,12 @@
+What:           /config/usb-gadget/gadget/functions/midi.name
+Date:           Nov 2014
+KernelVersion:  3.19
+Description:
+                The attributes:
+
+                index           - index value for the USB MIDI adapter
+                id              - ID string for the USB MIDI adapter
+                buflen          - MIDI buffer length
+                qlen            - USB read request queue length
+                in_ports        - number of MIDI input ports
+                out_ports       - number of MIDI output ports
diff --git a/Documentation/devicetree/bindings/usb/dwc3.txt b/Documentation/devicetree/bindings/usb/dwc3.txt
index 471366d6a129..cd7f0454e13a 100644
--- a/Documentation/devicetree/bindings/usb/dwc3.txt
+++ b/Documentation/devicetree/bindings/usb/dwc3.txt
@@ -14,6 +14,29 @@ Optional properties:
  - phys: from the *Generic PHY* bindings
  - phy-names: from the *Generic PHY* bindings
  - tx-fifo-resize: determines if the FIFO *has* to be reallocated.
+ - snps,disable_scramble_quirk: true when SW should disable data scrambling.
+        Only really useful for FPGA builds.
+ - snps,has-lpm-erratum: true when DWC3 was configured with LPM Erratum enabled
+ - snps,lpm-nyet-threshold: LPM NYET threshold
+ - snps,u2exit_lfps_quirk: set if we want to enable u2exit lfps quirk
+ - snps,u2ss_inp3_quirk: set if we enable P3 OK for U2/SS Inactive quirk
+ - snps,req_p1p2p3_quirk: when set, the core will always request for
+                        P1/P2/P3 transition sequence.
+ - snps,del_p1p2p3_quirk: when set core will delay P1/P2/P3 until a certain
+                        amount of 8B10B errors occur.
+ - snps,del_phy_power_chg_quirk: when set core will delay PHY power change
+                        from P0 to P1/P2/P3.
+ - snps,lfps_filter_quirk: when set core will filter LFPS reception.
+ - snps,rx_detect_poll_quirk: when set core will disable a 400us delay to start
+                        Polling LFPS after RX.Detect.
+ - snps,tx_de_emphasis_quirk: when set core will set Tx de-emphasis value.
+ - snps,tx_de_emphasis: the value driven to the PHY is controlled by the
+                        LTSSM during USB3 Compliance mode.
+ - snps,dis_u3_susphy_quirk: when set core will disable USB3 suspend phy.
+ - snps,dis_u2_susphy_quirk: when set core will disable USB2 suspend phy.
+ - snps,is-utmi-l1-suspend: true when DWC3 asserts output signal
+                        utmi_l1_suspend_n, false when asserts utmi_sleep_n
+ - snps,hird-threshold: HIRD threshold
 
 This is usually a subnode to DWC3 glue to which it is connected.
 
diff --git a/Documentation/devicetree/bindings/usb/exynos-usb.txt b/Documentation/devicetree/bindings/usb/exynos-usb.txt
index a3b5990d0f2c..9b4dbe3b2acc 100644
--- a/Documentation/devicetree/bindings/usb/exynos-usb.txt
+++ b/Documentation/devicetree/bindings/usb/exynos-usb.txt
@@ -82,8 +82,10 @@ Example:
 
 DWC3
 Required properties:
- - compatible: should be "samsung,exynos5250-dwusb3" for USB 3.0 DWC3
-               controller.
+ - compatible: should be one of the following -
+               "samsung,exynos5250-dwusb3": for USB 3.0 DWC3 controller on
+                                            Exynos5250/5420.
+               "samsung,exynos7-dwusb3": for USB 3.0 DWC3 controller on Exynos7.
  - #address-cells, #size-cells : should be '1' if the device has sub-nodes
                                  with 'reg' property.
  - ranges: allows valid 1:1 translation between child's address space and
diff --git a/Documentation/devicetree/bindings/usb/pxa-usb.txt b/Documentation/devicetree/bindings/usb/pxa-usb.txt
index 79729a948d5a..9c331799b87c 100644
--- a/Documentation/devicetree/bindings/usb/pxa-usb.txt
+++ b/Documentation/devicetree/bindings/usb/pxa-usb.txt
@@ -29,3 +29,25 @@ Example:
                 marvell,port-mode = <2>; /* PMM_GLOBAL_MODE */
         };
 
+UDC
+
+Required properties:
+ - compatible: Should be "marvell,pxa270-udc" for USB controllers
+   used in device mode.
+ - reg: usb device MMIO address space
+ - interrupts: single interrupt generated by the UDC IP
+ - clocks: input clock of the UDC IP (see clock-bindings.txt)
+
+Optional properties:
+ - gpios:
+   - gpio activated to control the USB D+ pullup (see gpio.txt)
+
+Example:
+
+                pxa27x_udc: udc@40600000 {
+                        compatible = "marvell,pxa270-udc";
+                        reg = <0x40600000 0x10000>;
+                        interrupts = <11>;
+                        clocks = <&pxa2xx_clks 11>;
+                        gpios = <&gpio 22 GPIO_ACTIVE_LOW>;
+                };
diff --git a/Documentation/usb/gadget_hid.txt b/Documentation/usb/gadget_hid.txt
index 12696c2e43fb..7a0fb8e16e27 100644
--- a/Documentation/usb/gadget_hid.txt
+++ b/Documentation/usb/gadget_hid.txt
@@ -74,6 +74,13 @@ static struct platform_device my_hid = {
         You can add as many HID functions as you want, only limited by
         the amount of interrupt endpoints your gadget driver supports.
 
+Configuration with configfs
+
+        Instead of adding fake platform devices and drivers in order to pass
+        some data to the kernel, if HID is a part of a gadget composed with
+        configfs the hidg_func_descriptor.report_desc is passed to the kernel
+        by writing the appropriate stream of bytes to a configfs attribute.
+
 Send and receive HID reports
 
         HID reports can be sent/received using read/write on the