summaryrefslogtreecommitdiff
path: root/drivers/ide/qd65xx.c
diff options
context:
space:
mode:
authorJacob Keller <jacob.e.keller@intel.com>2021-06-09 19:39:51 +0300
committerTony Nguyen <anthony.l.nguyen@intel.com>2021-06-11 18:47:41 +0300
commit67569a7f940130fcfe9041e07a614a5263a9944d (patch)
tree5fa926de32005737ad39b7baf72cf1deff8ef5a8 /drivers/ide/qd65xx.c
parent06c16d89d2cbe284c2792caa7648c052c1b91042 (diff)
downloadlinux-67569a7f940130fcfe9041e07a614a5263a9944d.tar.xz
ice: report the PTP clock index in ethtool .get_ts_info
Now that the driver registers a PTP clock device that represents the clock hardware, it is important that the clock index is reported via the ethtool .get_ts_info callback. The underlying hardware resource is shared between multiple PF functions. Only one function owns the hardware resources associated with a timer, but multiple functions may be associated with it for the purposes of timestamping. To support this, the owning PF will store the clock index into the driver shared parameters buffer in firmware. Other PFs will look up the clock index by reading the driver shared parameter on demand when requested via the .get_ts_info ethtool function. In this way, all functions which are tied to the same timer are able to report the clock index. Userspace software such as ptp4l performs a look up on the netdev to determine the associated clock, and all commands to control or configure the clock will be handled through the controlling PF. Signed-off-by: Jacob Keller <jacob.e.keller@intel.com> Tested-by: Tony Brelinski <tonyx.brelinski@intel.com> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
Diffstat (limited to 'drivers/ide/qd65xx.c')
0 files changed, 0 insertions, 0 deletions