blob: 22d06cfdb07660b14fb9528117f4f2171b0838a4 [file] [log] [blame]
Praveen Paneri337dc3a2012-11-23 16:03:06 +05301* Samsung's usb phy transceiver
2
3The Samsung's phy transceiver is used for controlling usb otg phy for
4s3c-hsotg usb device controller.
5TODO: Adding the PHY binding with controller(s) according to the under
6developement generic PHY driver.
7
8Required properties:
9- compatible : should be "samsung,exynos4210-usbphy"
10- reg : base physical address of the phy registers and length of memory mapped
11 region.
Vivek Gautam69f09462013-01-15 11:40:25 +053012
13Optional properties:
14- #address-cells: should be '1' when usbphy node has a child node with 'reg'
15 property.
16- #size-cells: should be '1' when usbphy node has a child node with 'reg'
17 property.
18- ranges: allows valid translation between child's address space and parent's
19 address space.
20
21- The child node 'usbphy-sys' to the node 'usbphy' is for the system controller
22 interface for usb-phy. It should provide the following information required by
23 usb-phy controller to control phy.
24 - reg : base physical address of PHY_CONTROL registers.
25 The size of this register is the total sum of size of all PHY_CONTROL
26 registers that the SoC has. For example, the size will be
27 '0x4' in case we have only one PHY_CONTROL register (e.g.
28 OTHERS register in S3C64XX or USB_PHY_CONTROL register in S5PV210)
29 and, '0x8' in case we have two PHY_CONTROL registers (e.g.
30 USBDEVICE_PHY_CONTROL and USBHOST_PHY_CONTROL registers in exynos4x).
31 and so on.
32
33Example:
34 - Exynos4210
35
36 usbphy@125B0000 {
37 #address-cells = <1>;
38 #size-cells = <1>;
39 compatible = "samsung,exynos4210-usbphy";
40 reg = <0x125B0000 0x100>;
41 ranges;
42
43 usbphy-sys {
44 /* USB device and host PHY_CONTROL registers */
45 reg = <0x10020704 0x8>;
46 };
47 };