From: Soumyadeep Hore <soumyadeep.hore@intel.com>
To: bruce.richardson@intel.com, aman.deep.singh@intel.com
Cc: dev@dpdk.org, Jun Zhang <xuejun.zhang@intel.com>
Subject: [PATCH v1] common/iavf: introduce hardware clock ID in PTP caps
Date: Wed, 15 Jan 2025 07:23:23 +0000 [thread overview]
Message-ID: <20250115072323.1117429-1-soumyadeep.hore@intel.com> (raw)
From: Jun Zhang <xuejun.zhang@intel.com>
When there are at least two VFs on a single adapter and both are used in
the same VM, each of them will register its own PTP clock. However, every
E810/E822 adapter has only one PHC clock that we use. In order to register
only one PTP clock, VFs need to identify HW and make sure they come from
the same board.
This patch adds a @hardware_clock_id that helps in this identification.
VFs from the same board should receive the same @hardware_clock_id and VFs
from two different boards should receive different IDs.
Signed-off-by: Jun Zhang <xuejun.zhang@intel.com>
Signed-off-by: Soumyadeep Hore <soumyadeep.hore@intel.com>
---
drivers/common/iavf/virtchnl.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/common/iavf/virtchnl.h b/drivers/common/iavf/virtchnl.h
index c0d52ddd32..f4ca2cc9f0 100644
--- a/drivers/common/iavf/virtchnl.h
+++ b/drivers/common/iavf/virtchnl.h
@@ -2224,6 +2224,7 @@ VIRTCHNL_CHECK_STRUCT_LEN(12, virtchnl_quanta_cfg);
#define VIRTCHNL_1588_PTP_CAP_PHC_REGS BIT(4)
#define VIRTCHNL_1588_PTP_CAP_SYNCE BIT(6)
#define VIRTCHNL_1588_PTP_CAP_GNSS BIT(7)
+#define VIRTCHNL_1588_PTP_CAP_HARDWARE_CLOCK_ID BIT(8)
struct virtchnl_phc_regs {
u32 clock_hi;
@@ -2248,7 +2249,8 @@ struct virtchnl_ptp_caps {
u8 n_per_out;
u8 n_pins;
u8 tx_tstamp_format;
- u8 rsvd[11];
+ u8 hardware_clock_id;
+ u8 rsvd[10];
};
VIRTCHNL_CHECK_STRUCT_LEN(48, virtchnl_ptp_caps);
--
2.43.0
reply other threads:[~2025-01-15 8:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250115072323.1117429-1-soumyadeep.hore@intel.com \
--to=soumyadeep.hore@intel.com \
--cc=aman.deep.singh@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=xuejun.zhang@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;
as well as URLs for NNTP newsgroup(s).