diff options
author | Rob Herring <robh@kernel.org> | 2015-09-26 00:26:58 -0400 |
---|---|---|
committer | Rob Herring <robh@kernel.org> | 2015-10-22 10:21:23 -0400 |
commit | 24aa40d3c122e57096a314b2503c1e4101f2e84f (patch) | |
tree | de7a64159a534c4516100610c16cc5fee216e00f | |
parent | d9d41df3e8ef39b7b2cfeb4e9a2ba5c7cf7cad88 (diff) |
dt-bindings: consolidate USB PHYs in bindings/phy
Move USB PHY bindings under usb directory to phy directory which already
contains other USB PHY bindings.
The Samsung USB PHY binding is obsolete and can be removed.
Signed-off-by: Rob Herring <robh@kernel.org>
Cc: Pawel Moll <pawel.moll@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Ian Campbell <ijc+devicetree@hellion.org.uk>
Cc: Kumar Gala <galak@codeaurora.org>
-rw-r--r-- | Documentation/devicetree/bindings/phy/keystone-usb-phy.txt (renamed from Documentation/devicetree/bindings/usb/keystone-phy.txt) | 0 | ||||
-rw-r--r-- | Documentation/devicetree/bindings/phy/mxs-usb-phy.txt (renamed from Documentation/devicetree/bindings/usb/mxs-phy.txt) | 0 | ||||
-rw-r--r-- | Documentation/devicetree/bindings/phy/nvidia,tegra20-usb-phy.txt (renamed from Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt) | 0 | ||||
-rw-r--r-- | Documentation/devicetree/bindings/phy/qcom,usb-8x16-phy.txt (renamed from Documentation/devicetree/bindings/usb/qcom,usb-8x16-phy.txt) | 0 | ||||
-rw-r--r-- | Documentation/devicetree/bindings/usb/samsung-usbphy.txt | 117 |
5 files changed, 0 insertions, 117 deletions
diff --git a/Documentation/devicetree/bindings/usb/keystone-phy.txt b/Documentation/devicetree/bindings/phy/keystone-usb-phy.txt index f37b3a86341d..f37b3a86341d 100644 --- a/Documentation/devicetree/bindings/usb/keystone-phy.txt +++ b/Documentation/devicetree/bindings/phy/keystone-usb-phy.txt | |||
diff --git a/Documentation/devicetree/bindings/usb/mxs-phy.txt b/Documentation/devicetree/bindings/phy/mxs-usb-phy.txt index 379b84a567cc..379b84a567cc 100644 --- a/Documentation/devicetree/bindings/usb/mxs-phy.txt +++ b/Documentation/devicetree/bindings/phy/mxs-usb-phy.txt | |||
diff --git a/Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt b/Documentation/devicetree/bindings/phy/nvidia,tegra20-usb-phy.txt index a9aa79fb90ed..a9aa79fb90ed 100644 --- a/Documentation/devicetree/bindings/usb/nvidia,tegra20-usb-phy.txt +++ b/Documentation/devicetree/bindings/phy/nvidia,tegra20-usb-phy.txt | |||
diff --git a/Documentation/devicetree/bindings/usb/qcom,usb-8x16-phy.txt b/Documentation/devicetree/bindings/phy/qcom,usb-8x16-phy.txt index 2cb2168cef41..2cb2168cef41 100644 --- a/Documentation/devicetree/bindings/usb/qcom,usb-8x16-phy.txt +++ b/Documentation/devicetree/bindings/phy/qcom,usb-8x16-phy.txt | |||
diff --git a/Documentation/devicetree/bindings/usb/samsung-usbphy.txt b/Documentation/devicetree/bindings/usb/samsung-usbphy.txt deleted file mode 100644 index 33fd3543f3f8..000000000000 --- a/Documentation/devicetree/bindings/usb/samsung-usbphy.txt +++ /dev/null | |||
@@ -1,117 +0,0 @@ | |||
1 | SAMSUNG USB-PHY controllers | ||
2 | |||
3 | ** Samsung's usb 2.0 phy transceiver | ||
4 | |||
5 | The Samsung's usb 2.0 phy transceiver is used for controlling | ||
6 | usb 2.0 phy for s3c-hsotg as well as ehci-s5p and ohci-exynos | ||
7 | usb controllers across Samsung SOCs. | ||
8 | TODO: Adding the PHY binding with controller(s) according to the under | ||
9 | development generic PHY driver. | ||
10 | |||
11 | Required properties: | ||
12 | |||
13 | Exynos4210: | ||
14 | - compatible : should be "samsung,exynos4210-usb2phy" | ||
15 | - reg : base physical address of the phy registers and length of memory mapped | ||
16 | region. | ||
17 | - clocks: Clock IDs array as required by the controller. | ||
18 | - clock-names: names of clock correseponding IDs clock property as requested | ||
19 | by the controller driver. | ||
20 | |||
21 | Exynos5250: | ||
22 | - compatible : should be "samsung,exynos5250-usb2phy" | ||
23 | - reg : base physical address of the phy registers and length of memory mapped | ||
24 | region. | ||
25 | |||
26 | Optional properties: | ||
27 | - #address-cells: should be '1' when usbphy node has a child node with 'reg' | ||
28 | property. | ||
29 | - #size-cells: should be '1' when usbphy node has a child node with 'reg' | ||
30 | property. | ||
31 | - ranges: allows valid translation between child's address space and parent's | ||
32 | address space. | ||
33 | |||
34 | - The child node 'usbphy-sys' to the node 'usbphy' is for the system controller | ||
35 | interface for usb-phy. It should provide the following information required by | ||
36 | usb-phy controller to control phy. | ||
37 | - reg : base physical address of PHY_CONTROL registers. | ||
38 | The size of this register is the total sum of size of all PHY_CONTROL | ||
39 | registers that the SoC has. For example, the size will be | ||
40 | '0x4' in case we have only one PHY_CONTROL register (e.g. | ||
41 | OTHERS register in S3C64XX or USB_PHY_CONTROL register in S5PV210) | ||
42 | and, '0x8' in case we have two PHY_CONTROL registers (e.g. | ||
43 | USBDEVICE_PHY_CONTROL and USBHOST_PHY_CONTROL registers in exynos4x). | ||
44 | and so on. | ||
45 | |||
46 | Example: | ||
47 | - Exynos4210 | ||
48 | |||
49 | usbphy@125B0000 { | ||
50 | #address-cells = <1>; | ||
51 | #size-cells = <1>; | ||
52 | compatible = "samsung,exynos4210-usb2phy"; | ||
53 | reg = <0x125B0000 0x100>; | ||
54 | ranges; | ||
55 | |||
56 | clocks = <&clock 2>, <&clock 305>; | ||
57 | clock-names = "xusbxti", "otg"; | ||
58 | |||
59 | usbphy-sys { | ||
60 | /* USB device and host PHY_CONTROL registers */ | ||
61 | reg = <0x10020704 0x8>; | ||
62 | }; | ||
63 | }; | ||
64 | |||
65 | |||
66 | ** Samsung's usb 3.0 phy transceiver | ||
67 | |||
68 | Starting exynso5250, Samsung's SoC have usb 3.0 phy transceiver | ||
69 | which is used for controlling usb 3.0 phy for dwc3-exynos usb 3.0 | ||
70 | controllers across Samsung SOCs. | ||
71 | |||
72 | Required properties: | ||
73 | |||
74 | Exynos5250: | ||
75 | - compatible : should be "samsung,exynos5250-usb3phy" | ||
76 | - reg : base physical address of the phy registers and length of memory mapped | ||
77 | region. | ||
78 | - clocks: Clock IDs array as required by the controller. | ||
79 | - clock-names: names of clocks correseponding to IDs in the clock property | ||
80 | as requested by the controller driver. | ||
81 | |||
82 | Optional properties: | ||
83 | - #address-cells: should be '1' when usbphy node has a child node with 'reg' | ||
84 | property. | ||
85 | - #size-cells: should be '1' when usbphy node has a child node with 'reg' | ||
86 | property. | ||
87 | - ranges: allows valid translation between child's address space and parent's | ||
88 | address space. | ||
89 | |||
90 | - The child node 'usbphy-sys' to the node 'usbphy' is for the system controller | ||
91 | interface for usb-phy. It should provide the following information required by | ||
92 | usb-phy controller to control phy. | ||
93 | - reg : base physical address of PHY_CONTROL registers. | ||
94 | The size of this register is the total sum of size of all PHY_CONTROL | ||
95 | registers that the SoC has. For example, the size will be | ||
96 | '0x4' in case we have only one PHY_CONTROL register (e.g. | ||
97 | OTHERS register in S3C64XX or USB_PHY_CONTROL register in S5PV210) | ||
98 | and, '0x8' in case we have two PHY_CONTROL registers (e.g. | ||
99 | USBDEVICE_PHY_CONTROL and USBHOST_PHY_CONTROL registers in exynos4x). | ||
100 | and so on. | ||
101 | |||
102 | Example: | ||
103 | usbphy@12100000 { | ||
104 | compatible = "samsung,exynos5250-usb3phy"; | ||
105 | reg = <0x12100000 0x100>; | ||
106 | #address-cells = <1>; | ||
107 | #size-cells = <1>; | ||
108 | ranges; | ||
109 | |||
110 | clocks = <&clock 1>, <&clock 286>; | ||
111 | clock-names = "ext_xtal", "usbdrd30"; | ||
112 | |||
113 | usbphy-sys { | ||
114 | /* USB device and host PHY_CONTROL registers */ | ||
115 | reg = <0x10040704 0x8>; | ||
116 | }; | ||
117 | }; | ||