From: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
To: donald.hunter@gmail.com, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
vadim.fedorenko@linux.dev, jiri@resnulli.us,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
andrew+netdev@lunn.ch, aleksandr.loktionov@intel.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
intel-wired-lan@lists.osuosl.org, linux-rdma@vger.kernel.org,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Subject: [PATCH net-next v1 0/3] dpll: add ref-sync pins feature
Date: Tue, 15 Apr 2025 19:51:12 +0200 [thread overview]
Message-ID: <20250415175115.1066641-1-arkadiusz.kubalewski@intel.com> (raw)
Allow to bind two pins and become a single source of clock signal, where
first of the pins is carring the base frequency and second provides SYNC
pulses.
Verify pins bind state/capabilities:
$ ./tools/net/ynl/pyynl/cli.py \
--spec Documentation/netlink/specs/dpll.yaml \
--do pin-get \
--json '{"id":0}'
{'board-label': 'CVL-SDP22',
'id': 0,
[...]
'reference-sync': [{'id': 1, 'state': 'disconnected'}],
[...]}
Bind the pins by setting connected state between them:
$ ./tools/net/ynl/pyynl/cli.py \
--spec Documentation/netlink/specs/dpll.yaml \
--do pin-set \
--json '{"id":0, "reference-sync":{"id":1, "state":"connected"}}'
Verify pins bind state:
$ ./tools/net/ynl/pyynl/cli.py \
--spec Documentation/netlink/specs/dpll.yaml \
--do pin-get \
--json '{"id":0}'
{'board-label': 'CVL-SDP22',
'id': 0,
[...]
'reference-sync': [{'id': 1, 'state': 'connected'}],
[...]}
Unbind the pins by setting disconnected state between them:
$ ./tools/net/ynl/pyynl/cli.py \
--spec Documentation/netlink/specs/dpll.yaml \
--do pin-set \
--json '{"id":0, "reference-sync":{"id":1, "state":"disconnected"}}'
Arkadiusz Kubalewski (3):
dpll: add reference-sync netlink attribute
dpll: add reference sync get/set
ice: add ref-sync dpll pins
Documentation/netlink/specs/dpll.yaml | 19 ++
drivers/dpll/dpll_core.c | 27 +++
drivers/dpll/dpll_core.h | 1 +
drivers/dpll/dpll_netlink.c | 188 ++++++++++++++++--
drivers/dpll/dpll_nl.c | 10 +-
drivers/dpll/dpll_nl.h | 1 +
.../net/ethernet/intel/ice/ice_adminq_cmd.h | 2 +
drivers/net/ethernet/intel/ice/ice_dpll.c | 186 +++++++++++++++++
include/linux/dpll.h | 10 +
include/uapi/linux/dpll.h | 1 +
10 files changed, 425 insertions(+), 20 deletions(-)
base-commit: 420aabef3ab5fa743afb4d3d391f03ef0e777ca8
--
2.38.1
next reply other threads:[~2025-04-15 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 17:51 Arkadiusz Kubalewski [this message]
2025-04-15 17:51 ` [PATCH net-next v1 1/3] dpll: add reference-sync netlink attribute Arkadiusz Kubalewski
2025-04-15 17:51 ` [PATCH net-next v1 2/3] dpll: add reference sync get/set Arkadiusz Kubalewski
2025-04-21 13:22 ` Simon Horman
2025-05-09 12:54 ` Kubalewski, Arkadiusz
2025-04-15 17:51 ` [PATCH net-next v1 3/3] ice: add ref-sync dpll pins Arkadiusz Kubalewski
2025-04-16 8:12 ` [PATCH net-next v1 0/3] dpll: add ref-sync pins feature Jiri Pirko
2025-04-16 13:01 ` Kubalewski, Arkadiusz
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=20250415175115.1066641-1-arkadiusz.kubalewski@intel.com \
--to=arkadiusz.kubalewski@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=vadim.fedorenko@linux.dev \
/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