Home
last modified time | relevance | path

Searched refs:PHC (Results 1 – 11 of 11) sorted by relevance

/Linux-v6.6/Documentation/ABI/testing/
Dsysfs-timecard17 Description: (RO) The list of available time sources that the PHC
58 PHC output PPS is from the PHC clock
62 IRIG output is from the PHC, in IRIG-B format
63 DCF output is from the PHC, in DCF format
76 the PHC. May be changed by writing one of the listed
246 Description: (RW) When retrieving the PHC with the PTP SYS_OFFSET_EXTENDED
247 ioctl, a system timestamp is made before and after the PHC
250 with the PHC time. This estimate may be wrong, as it depends
251 on PCI latencies, and when the PHC time was latched
255 retrieved PHC time.
[all …]
/Linux-v6.6/Documentation/driver-api/
Dptp.rst80 This function has a set of requirements from the PHC in order to be
83 * The PHC implements a servo algorithm internally that is used to
85 * When other PTP adjustment functions are called, the PHC servo
89 that 'jumps' the PHC clock time based on the provided offset. It
117 - Up to 4 independent PHC channels
124 … - Lock to GNSS input, automatic switching between GNSS and user-space PHC control (optional)
135 - PHC instances
/Linux-v6.6/Documentation/devicetree/bindings/net/
Dmscc-phy-vsc8531.txt35 hardware clock (PHC).
/Linux-v6.6/Documentation/networking/
Dtimestamping.rst627 There are situations when there may be more than one PHC (PTP Hardware Clock)
629 user to select which PHC to use for timestamping Ethernet frames. Instead, the
630 assumption is that the outermost PHC is always the most preferable, and that
652 I/O, they do have their own PHC). It is typical, but not mandatory, for all
653 interfaces of a DSA switch to share the same PHC.
773 But a MAC driver that is unaware of PHC stacking might get tripped up by
784 described above, in the case of a stacked PHC system, this condition should
785 never trigger, as this MAC is certainly not the outermost PHC. But this is
792 PHC system, this is incorrect because this MAC driver is not the only entity
800 that PTP timestamping is not enabled for anything other than the outermost PHC,
Dethtool-netlink.rst220 ``ETHTOOL_MSG_PHC_VCLOCKS_GET`` get PHC virtual clocks info
266 ``ETHTOOL_MSG_PHC_VCLOCKS_GET_REPLY`` PHC virtual clocks info
1236 ``ETHTOOL_A_TSINFO_PHC_INDEX`` is absent if there is no associated PHC (there
1622 Query device PHC virtual clocks information.
1634 ``ETHTOOL_A_PHC_VCLOCKS_NUM`` u32 PHC virtual clocks number
1635 ``ETHTOOL_A_PHC_VCLOCKS_INDEX`` s32 PHC index array
/Linux-v6.6/drivers/gpu/drm/radeon/
Dsumod.h201 # define PHC(x) ((x) << 0) macro
Dr600_dpm.c412 WREG32_P(CG_CTX_CGTT3D_R, PHC(p), ~PHC_MASK); in r600_set_ctxcgtt3d_rphc()
427 WREG32_P(CG_VDDC3D_OOR, PHC(p), ~PHC_MASK); in r600_set_vddc3d_oorphc()
Dr600d.h1421 # define PHC(x) ((x) << 0) macro
Dsumo_dpm.c139 WREG32(CG_GCOOR, PHC(grs) | SDC(p) | SU(u)); in sumo_program_grsd()
/Linux-v6.6/drivers/ptp/
DKconfig207 is exposed as PTP Hardware Clock (PHC) device to the Linux PTP
/Linux-v6.6/Documentation/networking/device_drivers/ethernet/intel/
Di40e.rst462 IEEE 1588 Precision Time Protocol (PTP) Hardware Clock (PHC)