-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge tag 'xceiv-for-v3.7' of git://git.kernel.org/pub/scm/linux/kern…
…el/git/balbi/usb into usb-next usb: xceiv: patches for v3.7 merge window nop xceiv got its own header to avoid polluting otg.h. It has also learned to work as USB2 and USB3 phys so we can use it on USB3 controllers. Together with those two changes to nop xceiv, we're adding basic PHY support to dwc3 driver, this is to allow platforms which actually have a SW-controllable PHY talk to them through dwc3 driver. We're adding a new phy driver for the OMAP architecture. This driver is for the PHY found in OMAP4 SoCs, and a new phy driver for the marvell architecture. An extra phy driver - for Tegra SoCs - is now moving from arch/arm/mach-tegra* to drivers/usb/phy. Also here, there's the creation of <linux/usb/phy.h> which should be used from now on for PHY drivers, even those which don't support OTG.
- Loading branch information
Showing
40 changed files
with
1,597 additions
and
603 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
USB COMPARATOR OF TWL CHIPS | ||
|
||
TWL6030 USB COMPARATOR | ||
- compatible : Should be "ti,twl6030-usb" | ||
- interrupts : Two interrupt numbers to the cpu should be specified. First | ||
interrupt number is the otg interrupt number that raises ID interrupts when | ||
the controller has to act as host and the second interrupt number is the | ||
usb interrupt number that raises VBUS interrupts when the controller has to | ||
act as device | ||
- usb-supply : phandle to the regulator device tree node. It should be vusb | ||
if it is twl6030 or ldousb if it is twl6025 subclass. | ||
|
||
twl6030-usb { | ||
compatible = "ti,twl6030-usb"; | ||
interrupts = < 4 10 >; | ||
}; | ||
|
||
Board specific device node entry | ||
&twl6030-usb { | ||
usb-supply = <&vusb>; | ||
}; | ||
|
||
TWL4030 USB PHY AND COMPARATOR | ||
- compatible : Should be "ti,twl4030-usb" | ||
- interrupts : The interrupt numbers to the cpu should be specified. First | ||
interrupt number is the otg interrupt number that raises ID interrupts | ||
and VBUS interrupts. The second interrupt number is optional. | ||
- <supply-name>-supply : phandle to the regulator device tree node. | ||
<supply-name> should be vusb1v5, vusb1v8 and vusb3v1 | ||
- usb_mode : The mode used by the phy to connect to the controller. "1" | ||
specifies "ULPI" mode and "2" specifies "CEA2011_3PIN" mode. | ||
|
||
twl4030-usb { | ||
compatible = "ti,twl4030-usb"; | ||
interrupts = < 10 4 >; | ||
usb1v5-supply = <&vusb1v5>; | ||
usb1v8-supply = <&vusb1v8>; | ||
usb3v1-supply = <&vusb3v1>; | ||
usb_mode = <1>; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
USB PHY | ||
|
||
OMAP USB2 PHY | ||
|
||
Required properties: | ||
- compatible: Should be "ti,omap-usb2" | ||
- reg : Address and length of the register set for the device. Also | ||
add the address of control module dev conf register until a driver for | ||
control module is added | ||
|
||
This is usually a subnode of ocp2scp to which it is connected. | ||
|
||
usb2phy@4a0ad080 { | ||
compatible = "ti,omap-usb2"; | ||
reg = <0x4a0ad080 0x58>, | ||
<0x4a002300 0x4>; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.