Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Vinicius Costa Gomes <vinicius.gomes@intel.com>
Cc: sasha.neftin@intel.com, netdev@vger.kernel.org,
	kurt@linutronix.de, linux-kernel@vger.kernel.org,
	Jakub Kicinski <kuba@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	daiweili@gmail.com, anthony.l.nguyen@intel.com,
	Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	intel-wired-lan@lists.osuosl.org, Paolo Abeni <pabeni@redhat.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [PATCH iwl-net v1] igb: Fix not clearing TimeSync interrupts for 82580
Date: Fri, 9 Aug 2024 22:04:01 -0700	[thread overview]
Message-ID: <Zrb0wdmIsksG38Uc@hoboy.vegasvil.org> (raw)
In-Reply-To: <20240810002302.2054816-1-vinicius.gomes@intel.com>

On Fri, Aug 09, 2024 at 05:23:02PM -0700, Vinicius Costa Gomes wrote:
> It was reported that 82580 NICs have a hardware bug that makes it
> necessary to write into the TSICR (TimeSync Interrupt Cause) register
> to clear it.

Bug, or was it a feature?

Or IOW, maybe i210 changed the semantics of the TSICR?

And what about the 82576?

Thanks,
Richard

  parent reply	other threads:[~2024-08-10  5:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-10  0:23 [Intel-wired-lan] [PATCH iwl-net v1] igb: Fix not clearing TimeSync interrupts for 82580 Vinicius Costa Gomes
2024-08-10  4:21 ` Paul Menzel
2024-08-10  5:04 ` Richard Cochran [this message]
2024-08-10 15:55   ` Daiwei Li
2024-08-12 17:59     ` Vinicius Costa Gomes
2024-08-13  3:35       ` [Intel-wired-lan] [PATCH iwl-net v2] " Daiwei Li
2024-08-13 22:26         ` Vinicius Costa Gomes
2024-08-14  4:58           ` Daiwei Li
2024-08-13  4:12 ` [Intel-wired-lan] [PATCH iwl-net v1] " Ratheesh Kannoth
2024-08-13 15:02   ` Jakub Kicinski

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=Zrb0wdmIsksG38Uc@hoboy.vegasvil.org \
    --to=richardcochran@gmail.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=daiweili@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=kurt@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=sasha.neftin@intel.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