From: Jakub Kicinski <kuba@kernel.org>
To: Sai Krishna <saikrishnag@marvell.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<sgoutham@marvell.com>, <gakula@marvell.com>,
<sbhatta@marvell.com>, <hkelam@marvell.com>,
<richardcochran@gmail.com>,
Naveen Mamindlapalli <naveenm@marvell.com>
Subject: Re: [net-next PATCH v2] octeontx2-pf: Use PTP HW timestamp counter atomic update feature
Date: Wed, 9 Aug 2023 15:50:22 -0700 [thread overview]
Message-ID: <20230809155022.132a69a7@kernel.org> (raw)
In-Reply-To: <20230807140535.3070350-1-saikrishnag@marvell.com>
On Mon, 7 Aug 2023 19:35:35 +0530 Sai Krishna wrote:
> Some of the newer silicon versions in CN10K series supports a feature
> where in the current PTP timestamp in HW can be updated atomically
> without losing any cpu cycles unlike read/modify/write register.
> This patch uses this feature so that PTP accuracy can be improved
> while adjusting the master offset in HW. There is no need for SW
> timecounter when using this feature. So removed references to SW
> timecounter wherever appropriate.
> -#include "ptp.h"
> #include "mbox.h"
> #include "rvu.h"
> +#include "ptp.h"
If you reorder the includes - maybe put them in alphabetical order?
> static bool cn10k_ptp_errata(struct ptp *ptp)
> {
> - if (ptp->pdev->subsystem_device == PCI_SUBSYS_DEVID_CN10K_A_PTP ||
> - ptp->pdev->subsystem_device == PCI_SUBSYS_DEVID_CNF10K_A_PTP)
> + if ((is_ptp_dev_cn10ka(ptp) &&
> + ((ptp->pdev->revision & 0x0F) == 0x0 || (ptp->pdev->revision & 0x0F) == 0x1)) ||
> + (is_ptp_dev_cnf10ka(ptp) &&
> + ((ptp->pdev->revision & 0x0F) == 0x0 || (ptp->pdev->revision & 0x0F) == 0x1)))
Please refactor the revision check to avoid these long lines repeating
the same logic
> return true;
> +
> return false;
> }
>
> -static bool is_ptp_tsfmt_sec_nsec(struct ptp *ptp)
> +static bool is_tstmp_atomic_update_supported(struct rvu *rvu)
> {
> - if (ptp->pdev->subsystem_device == PCI_SUBSYS_DEVID_CN10K_A_PTP ||
> - ptp->pdev->subsystem_device == PCI_SUBSYS_DEVID_CNF10K_A_PTP)
> - return true;
> - return false;
> + struct ptp *ptp = rvu->ptp;
> + struct pci_dev *pdev;
> +
> + if (is_rvu_otx2(rvu))
> + return false;
> +
> + pdev = ptp->pdev;
> +
> + /* On older silicon variants of CN10K, atomic update feature
> + * is not available.
> + */
> + if ((pdev->subsystem_device == PCI_SUBSYS_DEVID_CN10K_A_PTP &&
> + (pdev->revision & 0x0F) == 0x0) ||
> + (pdev->subsystem_device == PCI_SUBSYS_DEVID_CN10K_A_PTP &&
> + (pdev->revision & 0x0F) == 0x1) ||
> + (pdev->subsystem_device == PCI_SUBSYS_DEVID_CNF10K_A_PTP &&
> + (pdev->revision & 0x0F) == 0x0) ||
> + (pdev->subsystem_device == PCI_SUBSYS_DEVID_CNF10K_A_PTP &&
> + (pdev->revision & 0x0F) == 0x1))
why are you not using cn10k_ptp_errata() here?
> + return false;
> +
> + return true;
> }
> -static int otx2_ptp_adjtime(struct ptp_clock_info *ptp_info, s64 delta)
> +static int otx2_ptp_tc_adjtime(struct ptp_clock_info *ptp_info, s64 delta)
> {
> struct otx2_ptp *ptp = container_of(ptp_info, struct otx2_ptp,
> ptp_info);
> struct otx2_nic *pfvf = ptp->nic;
>
> + if (!ptp->nic)
> + return -ENODEV;
Is this check related to the rest of the patch?
> mutex_lock(&pfvf->mbox.lock);
> timecounter_adjtime(&ptp->time_counter, delta);
> mutex_unlock(&pfvf->mbox.lock);
--
pw-bot: cr
next prev parent reply other threads:[~2023-08-09 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 14:05 [net-next PATCH v2] octeontx2-pf: Use PTP HW timestamp counter atomic update feature Sai Krishna
2023-08-09 13:07 ` Kalesh Anakkur Purayil
2023-08-09 22:50 ` Jakub Kicinski [this message]
2023-08-11 5:48 ` Sai Krishna Gajula
2023-08-11 22:04 ` Jakub Kicinski
2023-08-14 11:33 ` Sai Krishna Gajula
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=20230809155022.132a69a7@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naveenm@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=saikrishnag@marvell.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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).