Searched refs:PHC (Results 1 – 10 of 10) sorted by relevance
/linux-6.3-rc2/Documentation/ABI/testing/ |
A D | sysfs-timecard | 17 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.3-rc2/Documentation/driver-api/ |
A D | ptp.rst | 101 - Up to 4 independent PHC channels 108 … - Lock to GNSS input, automatic switching between GNSS and user-space PHC control (optional)
|
/linux-6.3-rc2/Documentation/devicetree/bindings/net/ |
A D | mscc-phy-vsc8531.txt | 35 hardware clock (PHC).
|
/linux-6.3-rc2/Documentation/networking/ |
A D | timestamping.rst | 627 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,
|
A D | ethtool-netlink.rst | 220 ``ETHTOOL_MSG_PHC_VCLOCKS_GET`` get PHC virtual clocks info 266 ``ETHTOOL_MSG_PHC_VCLOCKS_GET_REPLY`` PHC virtual clocks info 1217 ``ETHTOOL_A_TSINFO_PHC_INDEX`` is absent if there is no associated PHC (there 1603 Query device PHC virtual clocks information. 1615 ``ETHTOOL_A_PHC_VCLOCKS_NUM`` u32 PHC virtual clocks number 1616 ``ETHTOOL_A_PHC_VCLOCKS_INDEX`` s32 PHC index array
|
/linux-6.3-rc2/drivers/gpu/drm/radeon/ |
A D | sumod.h | 201 # define PHC(x) ((x) << 0) macro
|
A D | r600_dpm.c | 412 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()
|
A D | r600d.h | 1421 # define PHC(x) ((x) << 0) macro
|
A D | sumo_dpm.c | 139 WREG32(CG_GCOOR, PHC(grs) | SDC(p) | SU(u)); in sumo_program_grsd()
|
/linux-6.3-rc2/Documentation/networking/device_drivers/ethernet/intel/ |
A D | i40e.rst | 462 IEEE 1588 Precision Time Protocol (PTP) Hardware Clock (PHC)
|
Completed in 42 milliseconds