Home
last modified time | relevance | path

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

/linux-6.15/Documentation/driver-api/
H A 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-6.15/Documentation/ABI/testing/
H A 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
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.
258 the estimated point where the FPGA latches the PHC time. This
[all …]
/linux-6.15/Documentation/devicetree/bindings/net/
H A Dmscc-phy-vsc8531.txt35 hardware clock (PHC).
/linux-6.15/Documentation/networking/
H A Dtimestamping.rst678 There are situations when there may be more than one PHC (PTP Hardware Clock)
680 user to select which PHC to use for timestamping Ethernet frames. Instead, the
681 assumption is that the outermost PHC is always the most preferable, and that
703 I/O, they do have their own PHC). It is typical, but not mandatory, for all
704 interfaces of a DSA switch to share the same PHC.
822 But a MAC driver that is unaware of PHC stacking might get tripped up by
833 described above, in the case of a stacked PHC system, this condition should
834 never trigger, as this MAC is certainly not the outermost PHC. But this is
841 PHC system, this is incorrect because this MAC driver is not the only entity
849 that PTP timestamping is not enabled for anything other than the outermost PHC,
H A Dxsk-tx-metadata.rst76 Hardware Clock (PHC) to ensure accuracy. AF_XDP takes a different data path
H A Dethtool-netlink.rst227 ``ETHTOOL_MSG_PHC_VCLOCKS_GET`` get PHC virtual clocks info
280 ``ETHTOOL_MSG_PHC_VCLOCKS_GET_REPLY`` PHC virtual clocks info
1278 ``ETHTOOL_A_TSINFO_PHC_INDEX`` is absent if there is no associated PHC (there
1684 Query device PHC virtual clocks information.
1696 ``ETHTOOL_A_PHC_VCLOCKS_NUM`` u32 PHC virtual clocks number
1697 ``ETHTOOL_A_PHC_VCLOCKS_INDEX`` s32 PHC index array
/linux-6.15/drivers/gpu/drm/radeon/
H A Dsumod.h201 # define PHC(x) ((x) << 0) macro
H A Dr600_dpm.c410 WREG32_P(CG_CTX_CGTT3D_R, PHC(p), ~PHC_MASK); in r600_set_ctxcgtt3d_rphc()
425 WREG32_P(CG_VDDC3D_OOR, PHC(p), ~PHC_MASK); in r600_set_vddc3d_oorphc()
H A Dr600d.h1421 # define PHC(x) ((x) << 0) macro
H A Dsumo_dpm.c137 WREG32(CG_GCOOR, PHC(grs) | SDC(p) | SU(u)); in sumo_program_grsd()
/linux-6.15/drivers/ptp/
H A DKconfig237 is exposed as PTP Hardware Clock (PHC) device to the Linux PTP
/linux-6.15/Documentation/networking/device_drivers/ethernet/intel/
H A Di40e.rst474 IEEE 1588 Precision Time Protocol (PTP) Hardware Clock (PHC)
/linux-6.15/Documentation/netlink/specs/
H A Dethtool.yaml2112 doc: Get PHC VCLOCKs.