From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Vinicius Costa Gomes <vinicius.gomes@intel.com>
Cc: Ferenc Fejes <ferenc.fejes@ericsson.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"marton12050@gmail.com" <marton12050@gmail.com>,
"peti.antal99@gmail.com" <peti.antal99@gmail.com>
Subject: Re: igc: missing HW timestamps at TX
Date: Mon, 15 Aug 2022 22:26:39 +0000 [thread overview]
Message-ID: <20220815222639.346wachaaq5zjwue@skbuf> (raw)
In-Reply-To: <87v8qti3u2.fsf@intel.com>
Hi Vinicius,
On Mon, Aug 15, 2022 at 02:39:33PM -0700, Vinicius Costa Gomes wrote:
> Just some aditional information (note that I know very little about
> interrupt internal workings), igc_intr_msi() is called when MSI-X is not
> enabled (i.e. "MSI only" system), igc_msix_other() is called when MSI-X
> is available. When MSI-X is available, i225/i226 sets up a separate
> interrupt handler for "general" events, the TX timestamp being available
> to be read from the registers is one those events.
Thanks for the extra information.
Why is the i225/i226 emitting an interrupt about the availability of a
new TX timestamp, if the igc driver polls for its availability anyway?
In other words, when IGC_TSICR_TXTS is found set, is a TX timestamp
available or is it not? Why does the driver schedule a deferred work
item to retrieve it?
next prev parent reply other threads:[~2022-08-16 5:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 14:42 igc: missing HW timestamps at TX Ferenc Fejes
2022-07-17 14:46 ` Ferenc Fejes
2022-07-18 14:46 ` Vinicius Costa Gomes
2022-07-19 7:40 ` Ferenc Fejes
2022-08-11 8:54 ` Ferenc Fejes
2022-08-11 13:33 ` Vinicius Costa Gomes
2022-08-12 14:13 ` Ferenc Fejes
2022-08-12 20:16 ` Vladimir Oltean
2022-08-15 6:47 ` Ferenc Fejes
2022-08-15 22:04 ` Vinicius Costa Gomes
2022-08-16 9:33 ` Vladimir Oltean
2022-08-17 7:44 ` Ferenc Fejes
2022-08-15 21:39 ` Vinicius Costa Gomes
2022-08-15 22:26 ` Vladimir Oltean [this message]
2022-08-15 23:07 ` Vinicius Costa Gomes
2022-08-16 8:51 ` Kurt Kanzenbach
2022-08-16 20:45 ` Vinicius Costa Gomes
2022-08-17 6:10 ` Kurt Kanzenbach
2022-08-17 19:24 ` Vinicius Costa Gomes
2022-08-16 9:10 ` Vladimir Oltean
2022-08-16 18:11 ` Vinicius Costa Gomes
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=20220815222639.346wachaaq5zjwue@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=ferenc.fejes@ericsson.com \
--cc=marton12050@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peti.antal99@gmail.com \
--cc=vinicius.gomes@intel.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