* [RFC PATCH 1/2] ptp: add control over HW timestamp latch point
2024-10-03 21:37 [RFC PATCH 0/2] ptp: add control over HW timestamp latch point Arkadiusz Kubalewski
@ 2024-10-03 21:37 ` Arkadiusz Kubalewski
2024-10-03 21:37 ` [RFC PATCH 2/2] ice: " Arkadiusz Kubalewski
2024-10-07 16:06 ` [RFC PATCH 0/2] " Richard Cochran
2 siblings, 0 replies; 5+ messages in thread
From: Arkadiusz Kubalewski @ 2024-10-03 21:37 UTC (permalink / raw)
To: netdev, linux-kernel, intel-wired-lan
Cc: anthony.l.nguyen, przemyslaw.kitszel, davem, edumazet, kuba,
pabeni, richardcochran, Arkadiusz Kubalewski
Introduce:
- ops for getting and setting the HW timestamp latch point,
- enumerate possible HW timestamp latch point,
- new sysfs ptp device attribute as user knob.
HW support of PTP/timesync solutions in network PHY chips can be
achieved with two different approaches, the timestamp maybe latched
either in the beginning or after the Start of Frame Delimiter (SFD) [1].
Allow ptp device drivers to provide user with control over the timestamp
latch point.
[1] https://www.ieee802.org/3/cx/public/april20/tse_3cx_01_0420.pdf
Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
---
drivers/ptp/ptp_sysfs.c | 44 ++++++++++++++++++++++++++++++++
include/linux/ptp_clock_kernel.h | 26 +++++++++++++++++++
2 files changed, 70 insertions(+)
diff --git a/drivers/ptp/ptp_sysfs.c b/drivers/ptp/ptp_sysfs.c
index 6b1b8f57cd95..7e9f6ef368b6 100644
--- a/drivers/ptp/ptp_sysfs.c
+++ b/drivers/ptp/ptp_sysfs.c
@@ -28,6 +28,46 @@ static ssize_t max_phase_adjustment_show(struct device *dev,
}
static DEVICE_ATTR_RO(max_phase_adjustment);
+static ssize_t ts_point_show(struct device *dev, struct device_attribute *attr,
+ char *page)
+{
+ struct ptp_clock *ptp = dev_get_drvdata(dev);
+ enum ptp_ts_point point;
+ int err;
+
+ if (!ptp->info->get_ts_point)
+ return -EOPNOTSUPP;
+ err = ptp->info->get_ts_point(ptp->info, &point);
+ if (err)
+ return err;
+
+ return sysfs_emit(page, "%d\n", point);
+}
+
+static ssize_t ts_point_store(struct device *dev, struct device_attribute *attr,
+ const char *buf, size_t count)
+{
+ struct ptp_clock *ptp = dev_get_drvdata(dev);
+ enum ptp_ts_point point;
+ int err;
+ u8 val;
+
+ if (!ptp->info->set_ts_point)
+ return -EOPNOTSUPP;
+ if (kstrtou8(buf, 0, &val))
+ return -EINVAL;
+ if (val > PTP_TS_POINT_MAX)
+ return -EINVAL;
+ point = val;
+
+ err = ptp->info->set_ts_point(ptp->info, point);
+ if (err)
+ return err;
+
+ return count;
+}
+static DEVICE_ATTR_RW(ts_point);
+
#define PTP_SHOW_INT(name, var) \
static ssize_t var##_show(struct device *dev, \
struct device_attribute *attr, char *page) \
@@ -335,6 +375,7 @@ static struct attribute *ptp_attrs[] = {
&dev_attr_pps_enable.attr,
&dev_attr_n_vclocks.attr,
&dev_attr_max_vclocks.attr,
+ &dev_attr_ts_point.attr,
NULL
};
@@ -363,6 +404,9 @@ static umode_t ptp_is_attribute_visible(struct kobject *kobj,
} else if (attr == &dev_attr_max_phase_adjustment.attr) {
if (!info->adjphase || !info->getmaxphase)
mode = 0;
+ } else if (attr == &dev_attr_ts_point.attr) {
+ if (!info->get_ts_point && !info->set_ts_point)
+ mode = 0;
}
return mode;
diff --git a/include/linux/ptp_clock_kernel.h b/include/linux/ptp_clock_kernel.h
index c892d22ce0a7..ee4b625bca2c 100644
--- a/include/linux/ptp_clock_kernel.h
+++ b/include/linux/ptp_clock_kernel.h
@@ -55,6 +55,20 @@ struct ptp_system_timestamp {
clockid_t clockid;
};
+/**
+ * enum ptp_ts_point - possible timestamp latch points (IEEE 802.3cx)
+ * PTP_TS_POINT_SFD: timestamp latched at the beginning of sending Start
+ * of Frame Delimiter (SFD)
+ * PTP_TS_POINT_POST_SFD: timestamp latched at the end of sending Start
+ * of Frame Delimiter (SFD)
+ */
+enum ptp_ts_point {
+ PTP_TS_POINT_SFD,
+ PTP_TS_POINT_POST_SFD,
+ __PTP_TS_POINT_MAX
+};
+#define PTP_TS_POINT_MAX (__PTP_TS_POINT_MAX - 1)
+
/**
* struct ptp_clock_info - describes a PTP hardware clock
*
@@ -159,6 +173,14 @@ struct ptp_system_timestamp {
* scheduling time (>=0) or negative value in case further
* scheduling is not required.
*
+ * @set_ts_point: Request change of timestamp latch point, as the timestamp
+ * could be latched at the beginning or at the end of start
+ * frame delimiter (SFD), as described in IEEE 802.3cx
+ * specification.
+ *
+ * @get_ts_point: Obtain the timestamp measurement latch point, counterpart of
+ * .set_ts_point() for getting currently configured value.
+ *
* Drivers should embed their ptp_clock_info within a private
* structure, obtaining a reference to it using container_of().
*
@@ -195,6 +217,10 @@ struct ptp_clock_info {
int (*verify)(struct ptp_clock_info *ptp, unsigned int pin,
enum ptp_pin_function func, unsigned int chan);
long (*do_aux_work)(struct ptp_clock_info *ptp);
+ int (*set_ts_point)(struct ptp_clock_info *ptp,
+ enum ptp_ts_point point);
+ int (*get_ts_point)(struct ptp_clock_info *ptp,
+ enum ptp_ts_point *point);
};
struct ptp_clock;
--
2.38.1
^ permalink raw reply [flat|nested] 5+ messages in thread* [RFC PATCH 2/2] ice: ptp: add control over HW timestamp latch point
2024-10-03 21:37 [RFC PATCH 0/2] ptp: add control over HW timestamp latch point Arkadiusz Kubalewski
2024-10-03 21:37 ` [RFC PATCH 1/2] " Arkadiusz Kubalewski
@ 2024-10-03 21:37 ` Arkadiusz Kubalewski
2024-10-07 16:06 ` [RFC PATCH 0/2] " Richard Cochran
2 siblings, 0 replies; 5+ messages in thread
From: Arkadiusz Kubalewski @ 2024-10-03 21:37 UTC (permalink / raw)
To: netdev, linux-kernel, intel-wired-lan
Cc: anthony.l.nguyen, przemyslaw.kitszel, davem, edumazet, kuba,
pabeni, richardcochran, Arkadiusz Kubalewski
Implement ptp HW timestamp latch points callbacks, allow user to control
the latch point of ptp timestamps in E825 devices.
Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
---
drivers/net/ethernet/intel/ice/ice_ptp.c | 48 +++++++++++++++++++
drivers/net/ethernet/intel/ice/ice_ptp_hw.c | 52 +++++++++++++++++++++
drivers/net/ethernet/intel/ice/ice_ptp_hw.h | 3 +-
3 files changed, 102 insertions(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/intel/ice/ice_ptp.c b/drivers/net/ethernet/intel/ice/ice_ptp.c
index ef2e858f49bb..b37374dc7daf 100644
--- a/drivers/net/ethernet/intel/ice/ice_ptp.c
+++ b/drivers/net/ethernet/intel/ice/ice_ptp.c
@@ -2494,6 +2494,50 @@ ice_ptp_setup_pins_e823(struct ice_pf *pf, struct ptp_clock_info *info)
info->n_ext_ts = 1;
}
+/**
+ * ice_get_ts_point - get the tx timestamp latch point
+ * @info: the driver's PTP info structure
+ * @point: return the configured tx timestamp latch point
+ *
+ * Return: 0 on success, negative on failure.
+ */
+static int
+ice_get_ts_point(struct ptp_clock_info *info, enum ptp_ts_point *point)
+{
+ struct ice_pf *pf = ptp_info_to_pf(info);
+ struct ice_hw *hw = &pf->hw;
+ bool sfd_ena;
+ int ret;
+
+ ice_ptp_lock(hw);
+ ret = ice_ptp_hw_ts_point_get(hw, &sfd_ena);
+ ice_ptp_unlock(hw);
+ if (!ret)
+ *point = sfd_ena ? PTP_TS_POINT_SFD : PTP_TS_POINT_POST_SFD;
+
+ return ret;
+}
+
+/**
+ * ice_set_ts_point - set the tx timestamp latch point
+ * @info: the driver's PTP info structure
+ * @point: requested tx timestamp latch point
+ */
+static int
+ice_set_ts_point(struct ptp_clock_info *info, enum ptp_ts_point point)
+{
+ bool sfd_ena = point == PTP_TS_POINT_SFD ? true : false;
+ struct ice_pf *pf = ptp_info_to_pf(info);
+ struct ice_hw *hw = &pf->hw;
+ int ret;
+
+ ice_ptp_lock(hw);
+ ret = ice_ptp_hw_ts_point_set(hw, sfd_ena);
+ ice_ptp_unlock(hw);
+
+ return ret;
+}
+
/**
* ice_ptp_set_funcs_e82x - Set specialized functions for E82x support
* @pf: Board private structure
@@ -2512,6 +2556,10 @@ ice_ptp_set_funcs_e82x(struct ice_pf *pf, struct ptp_clock_info *info)
boot_cpu_has(X86_FEATURE_TSC_KNOWN_FREQ))
info->getcrosststamp = ice_ptp_getcrosststamp_e82x;
#endif /* CONFIG_ICE_HWTS */
+ if (ice_is_e825c(&pf->hw)) {
+ info->set_ts_point = ice_set_ts_point;
+ info->get_ts_point = ice_get_ts_point;
+ }
}
/**
diff --git a/drivers/net/ethernet/intel/ice/ice_ptp_hw.c b/drivers/net/ethernet/intel/ice/ice_ptp_hw.c
index 3a33e6b9b313..65a31c1bc335 100644
--- a/drivers/net/ethernet/intel/ice/ice_ptp_hw.c
+++ b/drivers/net/ethernet/intel/ice/ice_ptp_hw.c
@@ -6220,3 +6220,55 @@ int ice_cgu_get_output_pin_state_caps(struct ice_hw *hw, u8 pin_id,
return 0;
}
+
+/**
+ * ice_ptp_hw_ts_point_get - check if tx timestamping is latched on/post SFD
+ * @hw: pointer to the HW struct
+ * @sfd_ena: on success true if tx timestamping latched at beginning of SFD,
+ * false if post sfd
+ *
+ * Return: 0 on success, negative on error
+ */
+int ice_ptp_hw_ts_point_get(struct ice_hw *hw, bool *sfd_ena)
+{
+ u8 port = hw->port_info->lport;
+ u32 val;
+ int err;
+
+ err = ice_read_mac_reg_eth56g(hw, port, PHY_MAC_XIF_MODE, &val);
+ if (err)
+ return err;
+ if (val | PHY_MAC_XIF_TS_SFD_ENA_M)
+ *sfd_ena = true;
+ else
+ *sfd_ena = false;
+
+ return err;
+}
+
+/**
+ * ice_ptp_hw_tx_ts_point_set - configure timestamping on/post SFD
+ * @hw: pointer to the HW struct
+ * @sfd_ena: true to enable timestamping at beginning of SFD, false post sfd
+ *
+ * Configure timestamping to measure at the beginning/post SFD
+ * (start frame delimiter).
+ */
+int ice_ptp_hw_ts_point_set(struct ice_hw *hw, bool sfd_ena)
+{
+ u8 port = hw->port_info->lport;
+ int err, val;
+
+ err = ice_read_mac_reg_eth56g(hw, port, PHY_MAC_XIF_MODE, &val);
+ if (err)
+ return err;
+ if ((val | PHY_MAC_XIF_TS_SFD_ENA_M && sfd_ena) ||
+ (!(val | PHY_MAC_XIF_TS_SFD_ENA_M) && !sfd_ena))
+ return -EINVAL;
+ if (sfd_ena)
+ val |= PHY_MAC_XIF_TS_SFD_ENA_M;
+ else
+ val &= ~PHY_MAC_XIF_TS_SFD_ENA_M;
+
+ return ice_write_mac_reg_eth56g(hw, port, PHY_MAC_XIF_MODE, val);
+}
diff --git a/drivers/net/ethernet/intel/ice/ice_ptp_hw.h b/drivers/net/ethernet/intel/ice/ice_ptp_hw.h
index 0852a34ade91..3cfe7431c1b0 100644
--- a/drivers/net/ethernet/intel/ice/ice_ptp_hw.h
+++ b/drivers/net/ethernet/intel/ice/ice_ptp_hw.h
@@ -346,7 +346,8 @@ void ice_ptp_init_hw(struct ice_hw *hw);
int ice_get_phy_tx_tstamp_ready(struct ice_hw *hw, u8 block, u64 *tstamp_ready);
int ice_ptp_one_port_cmd(struct ice_hw *hw, u8 configured_port,
enum ice_ptp_tmr_cmd configured_cmd);
-
+int ice_ptp_hw_ts_point_get(struct ice_hw *hw, bool *sfd_ena);
+int ice_ptp_hw_ts_point_set(struct ice_hw *hw, bool sfd_ena);
/* E822 family functions */
int ice_read_quad_reg_e82x(struct ice_hw *hw, u8 quad, u16 offset, u32 *val);
int ice_write_quad_reg_e82x(struct ice_hw *hw, u8 quad, u16 offset, u32 val);
--
2.38.1
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [RFC PATCH 0/2] ptp: add control over HW timestamp latch point
2024-10-03 21:37 [RFC PATCH 0/2] ptp: add control over HW timestamp latch point Arkadiusz Kubalewski
2024-10-03 21:37 ` [RFC PATCH 1/2] " Arkadiusz Kubalewski
2024-10-03 21:37 ` [RFC PATCH 2/2] ice: " Arkadiusz Kubalewski
@ 2024-10-07 16:06 ` Richard Cochran
2024-10-08 19:06 ` Kubalewski, Arkadiusz
2 siblings, 1 reply; 5+ messages in thread
From: Richard Cochran @ 2024-10-07 16:06 UTC (permalink / raw)
To: Arkadiusz Kubalewski
Cc: netdev, linux-kernel, intel-wired-lan, anthony.l.nguyen,
przemyslaw.kitszel, davem, edumazet, kuba, pabeni
On Thu, Oct 03, 2024 at 11:37:52PM +0200, Arkadiusz Kubalewski wrote:
> HW support of PTP/timesync solutions in network PHY chips can be
> achieved with two different approaches, the timestamp maybe latched
> either in the beginning or after the Start of Frame Delimiter (SFD) [1].
>
> Allow ptp device drivers to provide user with control over the timestamp
> latch point.
This looks okay to me.
Sorry for the late reply, but I'm travelling untill Oct 11 and may not
response to messages right away.
Thanks,
Richard
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: [RFC PATCH 0/2] ptp: add control over HW timestamp latch point
2024-10-07 16:06 ` [RFC PATCH 0/2] " Richard Cochran
@ 2024-10-08 19:06 ` Kubalewski, Arkadiusz
0 siblings, 0 replies; 5+ messages in thread
From: Kubalewski, Arkadiusz @ 2024-10-08 19:06 UTC (permalink / raw)
To: Richard Cochran
Cc: netdev, linux-kernel, intel-wired-lan, Nguyen, Anthony L,
Kitszel, Przemyslaw, davem, edumazet, kuba, pabeni
>From: Richard Cochran <richardcochran@gmail.com>
>Sent: Monday, October 7, 2024 6:07 PM
>
>On Thu, Oct 03, 2024 at 11:37:52PM +0200, Arkadiusz Kubalewski wrote:
>> HW support of PTP/timesync solutions in network PHY chips can be
>> achieved with two different approaches, the timestamp maybe latched
>> either in the beginning or after the Start of Frame Delimiter (SFD) [1].
>>
>> Allow ptp device drivers to provide user with control over the
>> timestamp latch point.
>
>This looks okay to me.
>
>Sorry for the late reply, but I'm travelling untill Oct 11 and may not
>response to messages right away.
>
>Thanks,
>Richard
Hi Richard,
Not a problem.
Great to hear that it looks good for you, I will prepare proper patches soon.
Thank you!
Arkadiusz
^ permalink raw reply [flat|nested] 5+ messages in thread