All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Michael Chan <michael.chan@broadcom.com>,
	Somnath Kotur <somnath.kotur@broadcom.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	netdev@vger.kernel.org, Pavan Chebbi <pavan.chebbi@broadcom.com>
Subject: Re: [PATCH net] bnxt_en: enable PTM function
Date: Tue, 11 Aug 2026 18:04:13 +0100	[thread overview]
Message-ID: <7d68bd52-29e4-4d60-94cc-4f15fefb47e9@linux.dev> (raw)
In-Reply-To: <CALs4sv17EUFZ8vG_7tC0aDJhVT1NbCk7xnzEET8ZZdoHrPW4ng@mail.gmail.com>

On 08/08/2026 05:39, Pavan Chebbi wrote:
>>> Ok I understand you now. Maybe it is fine to have
>>> pcie_ptm_enabled()/disabled() called for this version of the driver.
>>> Since FW currently always enables it, and these calls are harmless and
>>> turn off .getcrosststamp on platforms that don't support PTM, both FW
>>> and driver/kernel end up working in sync.
>>> Only thing I would argue is should this be done in bnxt_ptp_init() and
>>> clear()? Since as much as PTM is a PCIe feature, the cross timestamps
>>> are tied with PTP.
>>
>> It makes sense to have PCIe things tied together, because PTM is PCIe
>> feature. Cross timestamps configuration are already in ptp area of the
>> driver, so no need to change anything around it
> 
> OK. Fine with me.
> Reviewed-by: Pavan Chebbi <pavan.chebbi@broadcom.com>
> Thanks

Jakub, it looks like we have to drop fixes tag and apply it to net-next
as it has never worked on upstream kernel.

Sashiko's comments are not really valuable - underflow of
ptm_enabled_cnt may happen only right before the device structure is
freed, so it actually doesn't matter, all other drivers do not care
about ptm counter as well on destroy path. And validating result of
pci_enable_ptm() also makes no sense because we don't care about the
result, only thing we can do is to put debug message, but that can also
be figured out in run-time.


      reply	other threads:[~2026-08-11 17:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 20:18 [PATCH net] bnxt_en: enable PTM function Vadim Fedorenko
2026-08-06 20:35 ` Michael Chan
2026-08-06 20:45   ` Vadim Fedorenko
2026-08-07 12:51     ` Pavan Chebbi
2026-08-07 14:00       ` Vadim Fedorenko
2026-08-07 16:13         ` Pavan Chebbi
2026-08-07 19:27           ` Vadim Fedorenko
2026-08-08  4:39             ` Pavan Chebbi
2026-08-11 17:04               ` Vadim Fedorenko [this message]

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=7d68bd52-29e4-4d60-94cc-4f15fefb47e9@linux.dev \
    --to=vadim.fedorenko@linux.dev \
    --cc=andrew+netdev@lunn.ch \
    --cc=kuba@kernel.org \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=pavan.chebbi@broadcom.com \
    --cc=somnath.kotur@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.