blob: f648094abc35329bbb67114162e99ed289d90880 [file] [log] [blame]
Kumar Galab053dc52009-06-19 08:31:05 -05001PHY nodes
2
3Required properties:
4
5 - device_type : Should be "ethernet-phy"
6 - interrupts : <a b> where a is the interrupt number and b is a
7 field that represents an encoding of the sense and level
8 information for the interrupt. This should be encoded based on
9 the information in section 2) depending on the type of interrupt
10 controller you have.
11 - interrupt-parent : the phandle for the interrupt controller that
12 services interrupts for this device.
13 - reg : The ID number for the phy, usually a small integer
14 - linux,phandle : phandle for this node; likely referenced by an
15 ethernet controller node.
16
David Daney6bd47ac2012-06-27 07:33:36 +000017Optional Properties:
18
19- compatible: Compatible list, may contain
20 "ethernet-phy-ieee802.3-c22" or "ethernet-phy-ieee802.3-c45" for
21 PHYs that implement IEEE802.3 clause 22 or IEEE802.3 clause 45
22 specifications. If neither of these are specified, the default is to
23 assume clause 22. The compatible list may also contain other
24 elements.
Florian Fainelli9f2b0932013-12-05 14:52:16 -080025- max-speed: Maximum PHY supported speed (10, 100, 1000...)
David Daney6bd47ac2012-06-27 07:33:36 +000026
Kumar Galab053dc52009-06-19 08:31:05 -050027Example:
28
29ethernet-phy@0 {
David Daney6bd47ac2012-06-27 07:33:36 +000030 compatible = "ethernet-phy-ieee802.3-c22";
31 linux,phandle = <2452000>;
Kumar Galab053dc52009-06-19 08:31:05 -050032 interrupt-parent = <40000>;
33 interrupts = <35 1>;
34 reg = <0>;
35 device_type = "ethernet-phy";
36};