From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Meghana Malladi <m-malladi@ti.com>,
vigneshr@ti.com, horms@kernel.org, jan.kiszka@siemens.com,
diogo.ivo@siemens.com, pabeni@redhat.com, kuba@kernel.org,
edumazet@google.com, davem@davemloft.net, andrew+netdev@lunn.ch
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, srk@ti.com,
Roger Quadros <rogerq@kernel.org>,
danishanwar@ti.com
Subject: Re: [PATCH net] net: ti: iccsg-prueth: Fix 1 PPS sync
Date: Wed, 23 Oct 2024 11:22:36 +0100 [thread overview]
Message-ID: <3fe8183a-08d3-47d3-b1a1-0d84f7bf58b7@linux.dev> (raw)
In-Reply-To: <20241023091213.593351-1-m-malladi@ti.com>
On 23/10/2024 10:12, Meghana Malladi wrote:
> The first PPS latch time needs to be calculated by the driver
> (in rounded off seconds) and configured as the start time
> offset for the cycle. After synchronizing two PTP clocks
> running as master/slave, missing this would cause master
> and slave to start immediately with some milliseconds
> drift which causes the PPS signal to never synchronize with
> the PTP master.
>
> Fixes: 186734c15886 ("net: ti: icssg-prueth: add packet timestamping and ptp support")
> Signed-off-by: Meghana Malladi <m-malladi@ti.com>
> ---
> drivers/net/ethernet/ti/icssg/icssg_prueth.c | 12 ++++++++++--
> drivers/net/ethernet/ti/icssg/icssg_prueth.h | 11 +++++++++++
> 2 files changed, 21 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/ti/icssg/icssg_prueth.c b/drivers/net/ethernet/ti/icssg/icssg_prueth.c
> index 0556910938fa..6b2cd7c898d0 100644
> --- a/drivers/net/ethernet/ti/icssg/icssg_prueth.c
> +++ b/drivers/net/ethernet/ti/icssg/icssg_prueth.c
> @@ -411,6 +411,8 @@ static int prueth_perout_enable(void *clockops_data,
> struct prueth_emac *emac = clockops_data;
> u32 reduction_factor = 0, offset = 0;
> struct timespec64 ts;
> + u64 current_cycle;
> + u64 start_offset;
> u64 ns_period;
>
> if (!on)
> @@ -449,8 +451,14 @@ static int prueth_perout_enable(void *clockops_data,
> writel(reduction_factor, emac->prueth->shram.va +
> TIMESYNC_FW_WC_SYNCOUT_REDUCTION_FACTOR_OFFSET);
>
> - writel(0, emac->prueth->shram.va +
> - TIMESYNC_FW_WC_SYNCOUT_START_TIME_CYCLECOUNT_OFFSET);
> + current_cycle = icssg_readq(emac->prueth->shram.va +
> + TIMESYNC_FW_WC_CYCLECOUNT_OFFSET);
> +
> + /* Rounding of current_cycle count to next second */
> + start_offset = ((current_cycle / MSEC_PER_SEC) + 1) * MSEC_PER_SEC;
This looks more like roundup(current_cycle, MSEC_PER_SEC), let's use it
instead of open coding.
> +
> + icssg_writeq(start_offset, emac->prueth->shram.va +
> + TIMESYNC_FW_WC_SYNCOUT_START_TIME_CYCLECOUNT_OFFSET);
>
> return 0;
> }
> diff --git a/drivers/net/ethernet/ti/icssg/icssg_prueth.h b/drivers/net/ethernet/ti/icssg/icssg_prueth.h
> index 8722bb4a268a..a4af2dbcca31 100644
> --- a/drivers/net/ethernet/ti/icssg/icssg_prueth.h
> +++ b/drivers/net/ethernet/ti/icssg/icssg_prueth.h
> @@ -330,6 +330,17 @@ static inline int prueth_emac_slice(struct prueth_emac *emac)
> extern const struct ethtool_ops icssg_ethtool_ops;
> extern const struct dev_pm_ops prueth_dev_pm_ops;
>
> +static inline u64 icssg_readq(const void __iomem *addr)
> +{
> + return readl(addr) + ((u64)readl(addr + 4) << 32);
> +}
> +
> +static inline void icssg_writeq(u64 val, void __iomem *addr)
> +{
> + writel(lower_32_bits(val), addr);
> + writel(upper_32_bits(val), addr + 4);
> +}
> +
> /* Classifier helpers */
> void icssg_class_set_mac_addr(struct regmap *miig_rt, int slice, u8 *mac);
> void icssg_class_set_host_mac_addr(struct regmap *miig_rt, const u8 *mac);
>
> base-commit: 73840ca5ef361f143b89edd5368a1aa8c2979241
next prev parent reply other threads:[~2024-10-23 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 9:12 Meghana Malladi
2024-10-23 10:22 ` Vadim Fedorenko [this message]
2024-10-23 11:38 ` Meghana Malladi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3fe8183a-08d3-47d3-b1a1-0d84f7bf58b7@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=diogo.ivo@siemens.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-malladi@ti.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rogerq@kernel.org \
--cc=srk@ti.com \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®