Searched refs:PHC (Results 1 – 9 of 9) sorted by relevance
| /Linux-v5.10/Documentation/driver-api/ |
| 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-v5.10/Documentation/devicetree/bindings/net/ |
| D | mscc-phy-vsc8531.txt | 35 hardware clock (PHC).
|
| /Linux-v5.10/Documentation/networking/ |
| D | timestamping.rst | 596 There are situations when there may be more than one PHC (PTP Hardware Clock)
598 user to select which PHC to use for timestamping Ethernet frames. Instead, the
599 assumption is that the outermost PHC is always the most preferable, and that
621 I/O, they do have their own PHC). It is typical, but not mandatory, for all
622 interfaces of a DSA switch to share the same PHC.
727 But a MAC driver that is unaware of PHC stacking might get tripped up by
738 described above, in the case of a stacked PHC system, this condition should
739 never trigger, as this MAC is certainly not the outermost PHC. But this is
746 PHC system, this is incorrect because this MAC driver is not the only entity
754 that PTP timestamping is not enabled for anything other than the outermost PHC,
|
| D | ethtool-netlink.rst | 1096 ``ETHTOOL_A_TSINFO_PHC_INDEX`` is absent if there is no associated PHC (there
|
| /Linux-v5.10/drivers/gpu/drm/radeon/ |
| D | sumod.h | 201 # define PHC(x) ((x) << 0) macro
|
| 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()
|
| D | r600d.h | 1421 # define PHC(x) ((x) << 0) macro
|
| D | sumo_dpm.c | 139 WREG32(CG_GCOOR, PHC(grs) | SDC(p) | SU(u)); in sumo_program_grsd()
|
| /Linux-v5.10/Documentation/networking/device_drivers/ethernet/intel/ |
| D | i40e.rst | 462 IEEE 1588 Precision Time Protocol (PTP) Hardware Clock (PHC)
|
