Searched refs:PHC (Results 1 – 11 of 11) sorted by relevance
| /linux/Documentation/translations/zh_CN/networking/ |
| H A D | timestamping.rst | 550 在数据包的路径中可能存在多个 PHC(PTP 硬件时钟)。内核没有明确的机制允许用 551 户选择用于时间戳以太网帧的 PHC。相反,假设最外层的 PHC 始终是最优的,并且 552 内核驱动程序协作以实现这一目标。目前有 3 种堆叠 PHC 的情况,如下所示: 567 己的PHC)。典型地,但不是强制性地,所有DSA 交换机接口共享相同的 PHC。 649 堆叠 PHC 可能会暴露 MAC 驱动程序的错误,这些错误在未堆叠 PHC 时无法触发。一个 655 序还是 MII 总线嗅探设备驱动程序,都应该设置此标志。但一个未意识到 PHC 堆叠的 662 |= SKBTX_IN_PROGRESS``" 标志。注意:如上所述,在堆叠 PHC 系统中,此条件 663 不应触发,因为此 MAC 肯定不是最外层的 PHC。但这是典型的错误所在。传输继续 668 SKBTX_IN_PROGRESS``" 是否设置。在堆叠 PHC 系统中,这是错误的,因为此 MAC 674 外层 PHC 启用,此增强检查将避免向用户空间传递重复的 TX 时间戳。
|
| /linux/Documentation/ABI/testing/ |
| H 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 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/Documentation/driver-api/ |
| H A D | ptp.rst | 80 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/Documentation/networking/device_drivers/ethernet/amazon/ |
| H A D | ena.rst | 59 ena_phc.[ch] PTP hardware clock infrastructure (see `PHC`_ for more info) 227 .. _`PHC`: target in RX copybreak 229 PTP Hardware Clock (PHC) 236 **PHC support** 238 PHC depends on the PTP module, which needs to be either loaded as a module or compiled into the ker… 246 - If no output is provided, the ENA driver cannot be loaded with PHC support. 248 **PHC activation** 269 PHC support and capabilities can be verified using ethtool: 275 **PHC timestamp** 277 To retrieve PHC timestamp, use `ptp-userspace-api`_, usage example using `testptp`_: [all …]
|
| /linux/Documentation/networking/ |
| H A D | timestamping.rst | 678 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 D | xsk-tx-metadata.rst | 76 Hardware Clock (PHC) to ensure accuracy. AF_XDP takes a different data path
|
| /linux/drivers/gpu/drm/radeon/ |
| H A D | sumod.h | 201 # define PHC(x) ((x) << 0) macro
|
| H A D | r600_dpm.c | 410 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 D | r600d.h | 1421 # define PHC(x) ((x) << 0) macro
|
| H A D | sumo_dpm.c | 137 WREG32(CG_GCOOR, PHC(grs) | SDC(p) | SU(u)); in sumo_program_grsd()
|
| /linux/drivers/virtio/ |
| H A D | Kconfig | 220 userspace. The PHC sysfs attribute "clock_name" describes the clock
|