forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge tag 'usb-4.4-rc1' of git://git.kernel.org/pub/scm/linux/kernel/…
…git/gregkh/usb Pull USB updates from Greg KH: "Here is the big USB patchset for 4.4-rc1. As usual, most of the changes are in the gadget subsystem, and we removed a host controller for a device that is no longer in existance, and probably never was even made public. There is also other minor driver updates and new device ids, full details in the changelog. All of these have been in linux-next for a while" * tag 'usb-4.4-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb: (233 commits) USB: core: Codestyle fix in urb.c usb: misc: usb3503: Use i2c_add_driver helper macro usb: host: lpc32xx: don't unregister phy device usb: host: lpc32xx: balance clk enable/disable on removal usb: host: lpc32xx: fix warnings caused by enabling unprepared clock uwb: drp: Use setup_timer uwb: neh: Use setup_timer uwb: rsv: Use setup_timer USB: qcserial: add Sierra Wireless MC74xx/EM74xx usb: chipidea: otg: don't wait vbus drops below BSV when starts host chipidea: ci_hdrc_pci: use PCI_VDEVICE() instead of PCI_DEVICE() doc: dt-binding: ci-hdrc-usb2: split vendor specific properties usb: chipidea: imx: add imx6ul usb support doc: dt-binding: ci-hdrc-usb2: improve property description usb: chipidea: imx: add usb support for imx7d Doc: usb: ci-hdrc-usb2: Add phy-clkgate-delay-us entry usb: chipidea: Add support for 'phy-clkgate-delay-us' property usb: chipidea: Use extcon framework for VBUS and ID detect usb: gadget: net2280: restore ep_cfg after defect7374 workaround usb: dwc2: host: Fix use after free w/ simultaneous irqs ...
- Loading branch information
Showing
144 changed files
with
5,964 additions
and
10,544 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
47 changes: 47 additions & 0 deletions
47
Documentation/devicetree/bindings/phy/brcm,cygnus-pcie-phy.txt
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,47 @@ | ||
Broadcom Cygnus PCIe PHY | ||
|
||
Required properties: | ||
- compatible: must be "brcm,cygnus-pcie-phy" | ||
- reg: base address and length of the PCIe PHY block | ||
- #address-cells: must be 1 | ||
- #size-cells: must be 0 | ||
|
||
Each PCIe PHY should be represented by a child node | ||
|
||
Required properties For the child node: | ||
- reg: the PHY ID | ||
0 - PCIe RC 0 | ||
1 - PCIe RC 1 | ||
- #phy-cells: must be 0 | ||
|
||
Example: | ||
pcie_phy: phy@0301d0a0 { | ||
compatible = "brcm,cygnus-pcie-phy"; | ||
reg = <0x0301d0a0 0x14>; | ||
|
||
pcie0_phy: phy@0 { | ||
reg = <0>; | ||
#phy-cells = <0>; | ||
}; | ||
|
||
pcie1_phy: phy@1 { | ||
reg = <1>; | ||
#phy-cells = <0>; | ||
}; | ||
}; | ||
|
||
/* users of the PCIe phy */ | ||
|
||
pcie0: pcie@18012000 { | ||
... | ||
... | ||
phys = <&pcie0_phy>; | ||
phy-names = "pcie-phy"; | ||
}; | ||
|
||
pcie1: pcie@18013000 { | ||
... | ||
... | ||
phys = <pcie1_phy>; | ||
phy-names = "pcie-phy"; | ||
}; |
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,68 @@ | ||
mt65xx USB3.0 PHY binding | ||
-------------------------- | ||
|
||
This binding describes a usb3.0 phy for mt65xx platforms of Medaitek SoC. | ||
|
||
Required properties (controller (parent) node): | ||
- compatible : should be "mediatek,mt8173-u3phy" | ||
- reg : offset and length of register for phy, exclude port's | ||
register. | ||
- clocks : a list of phandle + clock-specifier pairs, one for each | ||
entry in clock-names | ||
- clock-names : must contain | ||
"u3phya_ref": for reference clock of usb3.0 analog phy. | ||
|
||
Required nodes : a sub-node is required for each port the controller | ||
provides. Address range information including the usual | ||
'reg' property is used inside these nodes to describe | ||
the controller's topology. | ||
|
||
Required properties (port (child) node): | ||
- reg : address and length of the register set for the port. | ||
- #phy-cells : should be 1 (See second example) | ||
cell after port phandle is phy type from: | ||
- PHY_TYPE_USB2 | ||
- PHY_TYPE_USB3 | ||
|
||
Example: | ||
|
||
u3phy: usb-phy@11290000 { | ||
compatible = "mediatek,mt8173-u3phy"; | ||
reg = <0 0x11290000 0 0x800>; | ||
clocks = <&apmixedsys CLK_APMIXED_REF2USB_TX>; | ||
clock-names = "u3phya_ref"; | ||
#address-cells = <2>; | ||
#size-cells = <2>; | ||
ranges; | ||
status = "okay"; | ||
|
||
phy_port0: port@11290800 { | ||
reg = <0 0x11290800 0 0x800>; | ||
#phy-cells = <1>; | ||
status = "okay"; | ||
}; | ||
|
||
phy_port1: port@11291000 { | ||
reg = <0 0x11291000 0 0x800>; | ||
#phy-cells = <1>; | ||
status = "okay"; | ||
}; | ||
}; | ||
|
||
Specifying phy control of devices | ||
--------------------------------- | ||
|
||
Device nodes should specify the configuration required in their "phys" | ||
property, containing a phandle to the phy port node and a device type; | ||
phy-names for each port are optional. | ||
|
||
Example: | ||
|
||
#include <dt-bindings/phy/phy.h> | ||
|
||
usb30: usb@11270000 { | ||
... | ||
phys = <&phy_port0 PHY_TYPE_USB3>; | ||
phy-names = "usb3-0"; | ||
... | ||
}; |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1300,6 +1300,13 @@ F: arch/arm/mach-mediatek/ | |
N: mtk | ||
K: mediatek | ||
|
||
ARM/Mediatek USB3 PHY DRIVER | ||
M: Chunfeng Yun <[email protected]> | ||
L: [email protected] (moderated for non-subscribers) | ||
L: [email protected] (moderated for non-subscribers) | ||
S: Maintained | ||
F: drivers/phy/phy-mt65xx-usb3.c | ||
|
||
ARM/MICREL KS8695 ARCHITECTURE | ||
M: Greg Ungerer <[email protected]> | ||
L: [email protected] (moderated for non-subscribers) | ||
|
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.