6f18ce8026
Add snapshot of device tree bindings from keystone common kernel, branch
"android-mainline-keystone-qcom-release" at c4c12103f9c0 ("Snap for 9228065
from e32903b9a63bb558df8b803b076619c53c16baad to
android-mainline-keystone-qcom-release").
Change-Id: I7682079615cbd9f29340a5c1f2a1d84ec441a1f1
Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
43 lines
1.2 KiB
Plaintext
43 lines
1.2 KiB
Plaintext
Time stamps from MII bus snooping devices
|
|
|
|
This binding supports non-PHY devices that snoop the MII bus and
|
|
provide time stamps. In contrast to PHY time stamping drivers (which
|
|
can simply attach their interface directly to the PHY instance), stand
|
|
alone MII time stamping drivers use this binding to specify the
|
|
connection between the snooping device and a given network interface.
|
|
|
|
Non-PHY MII time stamping drivers typically talk to the control
|
|
interface over another bus like I2C, SPI, UART, or via a memory mapped
|
|
peripheral. This controller device is associated with one or more
|
|
time stamping channels, each of which snoops on a MII bus.
|
|
|
|
The "timestamper" property lives in a phy node and links a time
|
|
stamping channel from the controller device to that phy's MII bus.
|
|
|
|
Example:
|
|
|
|
tstamper: timestamper@10000000 {
|
|
compatible = "ines,ptp-ctrl";
|
|
reg = <0x10000000 0x80>;
|
|
};
|
|
|
|
ethernet@20000000 {
|
|
mdio {
|
|
ethernet-phy@1 {
|
|
timestamper = <&tstamper 0>;
|
|
};
|
|
};
|
|
};
|
|
|
|
ethernet@30000000 {
|
|
mdio {
|
|
ethernet-phy@2 {
|
|
timestamper = <&tstamper 1>;
|
|
};
|
|
};
|
|
};
|
|
|
|
In this example, time stamps from the MII bus attached to phy@1 will
|
|
appear on time stamp channel 0 (zero), and those from phy@2 appear on
|
|
channel 1.
|