From: Simon Horman <simon.horman@corigine.com>
To: Yuezhen Luan <eggcar.luan@gmail.com>
Cc: jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
jacob.e.keller@intel.com
Subject: Re: [PATCH] igb: Fix extts capture value format for 82580/i354/i350
Date: Thu, 1 Jun 2023 00:01:11 +0200 [thread overview]
Message-ID: <ZHfDp21V3zy9kuE3@corigine.com> (raw)
In-Reply-To: <20230531090805.3959-1-eggcar.luan@gmail.com>
On Wed, May 31, 2023 at 09:08:05AM +0000, Yuezhen Luan wrote:
> 82580/i354/i350 features circle-counter-like timestamp registers
> that are different with newer i210. The EXTTS capture value in
> AUXTSMPx should be converted from raw circle counter value to
> timestamp value in resolution of 1 nanosec by the driver.
>
> Signed-off-by: Yuezhen Luan <eggcar.luan@gmail.com>
> ---
> drivers/net/ethernet/intel/igb/igb_main.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/igb/igb_main.c b/drivers/net/ethernet/intel/igb/igb_main.c
> index 58872a4c2..187daa8ef 100644
> --- a/drivers/net/ethernet/intel/igb/igb_main.c
> +++ b/drivers/net/ethernet/intel/igb/igb_main.c
> @@ -6947,6 +6947,7 @@ static void igb_extts(struct igb_adapter *adapter, int tsintr_tt)
> struct e1000_hw *hw = &adapter->hw;
> struct ptp_clock_event event;
> struct timespec64 ts;
> + unsigned long flags;
>
> if (pin < 0 || pin >= IGB_N_SDP)
> return;
> @@ -6954,9 +6955,12 @@ static void igb_extts(struct igb_adapter *adapter, int tsintr_tt)
> if (hw->mac.type == e1000_82580 ||
> hw->mac.type == e1000_i354 ||
> hw->mac.type == e1000_i350) {
> - s64 ns = rd32(auxstmpl);
> + u64 ns = rd32(auxstmpl);
>
> - ns += ((s64)(rd32(auxstmph) & 0xFF)) << 32;
> + ns += ((u64)(rd32(auxstmph) & 0xFF)) << 32;
> + spin_lock_irqsave(&adapter->tc, ns);
> + ns = timecounter_cyc2time(&adapter->tc, ns);
> + spin_unlock_irqrestore(&adapter->tc, ns);
Hi Yuezhen Luan,
unfortunately this doesn't compile because the arguments to
spin_lock_irqsave/spin_unlock_irqrestore are wrong.
> ts = ns_to_timespec64(ns);
> } else {
> ts.tv_nsec = rd32(auxstmpl);
--
pw-bot: cr
next prev parent reply other threads:[~2023-05-31 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 9:08 Yuezhen Luan
2023-05-31 22:01 ` Simon Horman [this message]
2023-06-01 5:33 ` [Intel-wired-lan] " Paul Menzel
[not found] ` <CACMC4jY=c8kBwxRjLL++ro=Zz1O54h5Y6ADU6x+46pgN8XhkpA@mail.gmail.com>
2023-06-01 6:14 ` Paul Menzel
2023-06-01 1:59 Yuezhen Luan
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=ZHfDp21V3zy9kuE3@corigine.com \
--to=simon.horman@corigine.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eggcar.luan@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
Powered by JetHome