From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: "Keller, Jacob E" <jacob.e.keller@intel.com>,
Yuezhen Luan <eggcar.luan@gmail.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>
Cc: "intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] igb: Fix extts capture value format for 82580/i354/i350
Date: Thu, 1 Jun 2023 13:45:10 -0700 [thread overview]
Message-ID: <22e193f7-b55d-a31a-0179-4a53af692a89@intel.com> (raw)
In-Reply-To: <CO1PR11MB5089465F5D37EBA62BB1A123D6499@CO1PR11MB5089.namprd11.prod.outlook.com>
On 6/1/2023 10:05 AM, Keller, Jacob E wrote:
>
>
>> -----Original Message-----
>> From: Yuezhen Luan <eggcar.luan@gmail.com>
>> Sent: Thursday, June 1, 2023 12:01 AM
>> To: Brandeburg, Jesse <jesse.brandeburg@intel.com>; Nguyen, Anthony L
>> <anthony.l.nguyen@intel.com>; davem@davemloft.net;
>> edumazet@google.com; kuba@kernel.org; pabeni@redhat.com
>> Cc: intel-wired-lan@lists.osuosl.org; netdev@vger.kernel.org; linux-
>> kernel@vger.kernel.org; Keller, Jacob E <jacob.e.keller@intel.com>; Yuezhen
>> Luan <eggcar.luan@gmail.com>
>> Subject: [PATCH v2] igb: Fix extts capture value format for 82580/i354/i350
>>
>> 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.
>>
>> This issue can be reproduced on i350 nics, connecting an 1PPS
>> signal to a SDP pin, and run 'ts2phc' command to read external
>> 1PPS timestamp value. On i210 this works fine, but on i350 the
>> extts is not correctly converted.
>>
>> The i350/i354/82580's SYSTIM and other timestamp registers are
>> 40bit counters, presenting time range of 2^40 ns, that means these
>> registers overflows every about 1099s. This causes all these regs
>> can't be used directly in contrast to the newer i210/i211s.
>>
>> The igb driver needs to convert these raw register values to
>> valid time stamp format by using kernel timecounter apis for i350s
>> families. Here the igb_extts() just forgot to do the convert.
>>
>> Signed-off-by: Yuezhen Luan <eggcar.luan@gmail.com>
>
> Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
Thanks for reviewing Jake.
> Thanks for fixing this!
>
> @Nguyen, Anthony L
> I think this is a worthy net fix.
Hi Yuezhen,
Could you include a Fixes: so that we can route this through net.
You should also add a target tree for your patch (net or net-next).
Here's some useful intro information for netdev [1].
Thanks,
Tony
[1]
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html#netdev-faq
next prev parent reply other threads:[~2023-06-01 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 7:00 [PATCH v2] igb: Fix extts capture value format for 82580/i354/i350 Yuezhen Luan
2023-06-01 17:05 ` Keller, Jacob E
2023-06-01 20:45 ` Tony Nguyen [this message]
2023-06-02 6:28 ` egg car
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=22e193f7-b55d-a31a-0179-4a53af692a89@intel.com \
--to=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;
as well as URLs for NNTP newsgroup(s).