diff options
author | Ederson de Souza <ederson.desouza@intel.com> | 2021-02-18 17:31:04 -0800 |
---|---|---|
committer | Tony Nguyen <anthony.l.nguyen@intel.com> | 2021-04-16 13:15:45 -0700 |
commit | 87938851b6efb6d5b44ae93c83226c6f991d5cc1 (patch) | |
tree | 8c4a005798690a7c74e6cfe48f98d4d2eb74aa07 /drivers/net/ethernet/intel/ixgbevf/ethtool.c | |
parent | 64433e5bf40abf893c7edbc60899bdcdd7c70b76 (diff) | |
download | linux-87938851b6efb6d5b44ae93c83226c6f991d5cc1.tar.bz2 |
igc: enable auxiliary PHC functions for the i225
The i225 device offers a number of special PTP Hardware Clock features on
the Software Defined Pins (SDPs) - much like i210, which is used as
inspiration for this patch. It enables two possible functions, namely
time stamping external events and periodic output signals.
The assignment of PHC functions to the four SDP can be freely chosen by
the user.
For the external events time stamping, when the SDP (configured as input
by user) level changes, an interrupt is generated and the kernel
Precision Time Protocol (PTP) is informed.
For the periodic output signals, the i225 is configured to generate them
(so the SDP level will change periodically) and the driver also has to
keep updating the time of the next level change. However, this work is
not necessary for some frequencies as the i225 takes care of them
(namely, anything with a half-cycle of 500ms, 250ms, 125ms or < 70ms).
While i225 allows up to four timers to be used to source the time used
on the external events or output signals, this patch uses only one of
those timers. Main reason is to keep it simple, as it's not clear how
these extra timers would be exposed to users. Note that currently a NIC
can expose a single PTP device.
Signed-off-by: Ederson de Souza <ederson.desouza@intel.com>
Tested-by: Dvora Fuxbrumer <dvorax.fuxbrumer@linux.intel.com>
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
Diffstat (limited to 'drivers/net/ethernet/intel/ixgbevf/ethtool.c')
0 files changed, 0 insertions, 0 deletions