Searched full:phc (Results 1 – 13 of 13) sorted by relevance
| /Documentation/driver-api/ |
| 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
|
| /Documentation/ABI/testing/ |
| 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 …]
|
| /Documentation/devicetree/bindings/ptp/ |
| D | ptp-idt82p33.yaml | 41 phc@51 {
|
| D | ptp-idtcm.yaml | 65 phc@5b {
|
| D | fsl,ptp.yaml | 144 phc@24e00 {
|
| /Documentation/networking/ |
| D | timestamping.rst | 646 There are situations when there may be more than one PHC (PTP Hardware Clock)
648 user to select which PHC to use for timestamping Ethernet frames. Instead, the
649 assumption is that the outermost PHC is always the most preferable, and that
671 I/O, they do have their own PHC). It is typical, but not mandatory, for all
672 interfaces of a DSA switch to share the same PHC.
792 But a MAC driver that is unaware of PHC stacking might get tripped up by
803 described above, in the case of a stacked PHC system, this condition should
804 never trigger, as this MAC is certainly not the outermost PHC. But this is
811 PHC system, this is incorrect because this MAC driver is not the only entity
819 that PTP timestamping is not enabled for anything other than the outermost PHC,
|
| D | ethtool-netlink.rst | 227 ``ETHTOOL_MSG_PHC_VCLOCKS_GET`` get PHC virtual clocks info
277 ``ETHTOOL_MSG_PHC_VCLOCKS_GET_REPLY`` PHC virtual clocks info
1260 ``ETHTOOL_A_TSINFO_PHC_INDEX`` is absent if there is no associated PHC (there
1659 Query device PHC virtual clocks information.
1671 ``ETHTOOL_A_PHC_VCLOCKS_NUM`` u32 PHC virtual clocks number
1672 ``ETHTOOL_A_PHC_VCLOCKS_INDEX`` s32 PHC index array
|
| /Documentation/netlink/specs/ |
| D | ethtool.yaml | 660 name: phc-index
935 name: phc-vclocks
1587 - phc-index
1716 name: phc-vclocks-get
1717 doc: Get PHC VCLOCKs.
1719 attribute-set: phc-vclocks
1721 do: &phc-vclocks-get-op
1729 dump: *phc-vclocks-get-op
|
| /Documentation/devicetree/bindings/net/ |
| D | fsl,fman.yaml | 135 '^phc@[a-f0-9]+$':
199 ptp_timer: phc@fe000 {
|
| D | mscc-phy-vsc8531.txt | 35 hardware clock (PHC).
|
| /Documentation/translations/zh_CN/core-api/ |
| D | printk-formats.rst | 267 %*phC 00:01:02: ... :3f
|
| /Documentation/core-api/ |
| D | printk-formats.rst | 289 %*phC 00:01:02: ... :3f
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| D | i40e.rst | 462 IEEE 1588 Precision Time Protocol (PTP) Hardware Clock (PHC)
|