Skip to content

Commit 56ef908

Browse files
authored
Merge pull request #95522 from openshift-cherrypick-robot/cherry-pick-95044-to-enterprise-4.17
[enterprise-4.17] TELCODOCS#2164: Added pin information
2 parents 10729a9 + 3a9a70d commit 56ef908

File tree

2 files changed

+49
-2
lines changed

2 files changed

+49
-2
lines changed

modules/nw-ptp-dual-wpc-hardware-config-reference.adoc

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,3 +36,25 @@ The value that you configure depends on your specific measurements and SMA1 cabl
3636
|`spec.profile.ptp4lConf`
3737
|Set the value of `boundary_clock_jbod` to 1 to enable support for multiple NICs.
3838
|====
39+
40+
Each value in the `spec.profile.plugins.e810.pins` list follows the `<function>` `<channel_number>` format.
41+
42+
Where:
43+
44+
`<function>`: Specifies the pin role. The following values are associated with the pin role:
45+
46+
* `0`: Disabled
47+
* `1`: Receive (Rx) – for 1PPS IN
48+
* `2`: Transmit (Tx) – for 1PPS OUT
49+
50+
`<channel_number>`: A number associated with the physical connector. The following channel numbers are associated with the physical connectors:
51+
52+
* `1`: `SMA1` or `U.FL1`
53+
* `2`: `SMA2` or `U.FL2`
54+
55+
Examples:
56+
57+
* `2 1`: Enables `1PPS OUT` (Tx) on `SMA1`.
58+
* `1 1`: Enables `1PPS IN` (Rx) on `SMA1`.
59+
60+
The PTP Operator passes these values to the Intel E810 hardware plugin and writes them to the sysfs pin configuration interface on each NIC.

modules/nw-ptp-e810-hardware-configuration-reference.adoc

Lines changed: 27 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,35 @@ The `SMA1` connector is bidirectional.
2424
The `SMA2` connector is bidirectional.
2525
|====
2626

27+
You can set the pin configuration on the Intel E810 NIC by using the `spec.profile.plugins.e810.pins` parameters as shown in the following example:
28+
[source,yaml]
29+
----
30+
pins:
31+
<interface_name>:
32+
<connector_name>: <function> <channel_number>
33+
----
34+
35+
Where:
36+
37+
`<function>`: Specifies the role of the pin. The following values are associated with the pin role:
38+
39+
* `0`: Disabled
40+
* `1`: Rx (Receive timestamping)
41+
* `2`: Tx (Transmit timestamping)
42+
43+
`<channel number>`: A number associated with the physical connector. The following channel numbers are associated with the physical connectors:
44+
45+
* `1`: `SMA1` or `U.FL1`
46+
* `2`: `SMA2` or `U.FL2`
47+
48+
Examples:
49+
50+
* `0 1`: Disables the pin mapped to `SMA1` or `U.FL1`.
51+
* `1 2`: Assigns the Rx function to `SMA2` or `U.FL2`.
52+
2753
[NOTE]
2854
====
29-
`SMA1` and `U.FL1` connectors share channel one.
30-
`SMA2` and `U.FL2` connectors share channel two.
55+
`SMA1` and `U.FL1` connectors share channel one. `SMA2` and `U.FL2` connectors share channel two.
3156
====
3257

3358
Set `spec.profile.plugins.e810.ublxCmds` parameters to configure the GNSS clock in the `PtpConfig` custom resource (CR).

0 commit comments

Comments
 (0)