From: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
To: netdev@vger.kernel.org
Cc: jiri@resnulli.us, corbet@lwn.net,
intel-wired-lan@lists.osuosl.org, linux-doc@vger.kernel.org,
jesse.brandeburg@intel.com,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
anthony.l.nguyen@intel.com, kuba@kernel.org,
vadim.fedorenko@linux.dev, pabeni@redhat.com,
davem@davemloft.net
Subject: [Intel-wired-lan] [PATCH net-next 0/4] dpll: add phase-offset and phase-adjust
Date: Wed, 27 Sep 2023 11:24:31 +0200 [thread overview]
Message-ID: <20230927092435.1565336-1-arkadiusz.kubalewski@intel.com> (raw)
Improve monitoring and control over dpll devices.
Allow user to receive measurement of phase difference between signals on
pin and dpll (phase-offset).
Allow user to receive and control adjustable value of pin's signal
phase (phase-adjust).
Arkadiusz Kubalewski (4):
dpll: docs: add support for pin signal phase offset/adjust
dpll: spec: add support for pin-dpll signal phase offset/adjust
dpll: netlink/core: add support for pin-dpll signal phase
offset/adjust
ice: dpll: implement phase related callbacks
Documentation/driver-api/dpll.rst | 53 ++++-
Documentation/netlink/specs/dpll.yaml | 33 +++-
drivers/dpll/dpll_netlink.c | 99 +++++++++-
drivers/dpll/dpll_nl.c | 8 +-
drivers/dpll/dpll_nl.h | 2 +-
drivers/net/ethernet/intel/ice/ice_dpll.c | 224 +++++++++++++++++++++-
drivers/net/ethernet/intel/ice/ice_dpll.h | 10 +-
include/linux/dpll.h | 18 ++
include/uapi/linux/dpll.h | 8 +-
9 files changed, 443 insertions(+), 12 deletions(-)
--
2.38.1
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next reply other threads:[~2023-09-27 9:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 9:24 Arkadiusz Kubalewski [this message]
2023-09-27 9:24 ` [Intel-wired-lan] [PATCH net-next 1/4] dpll: docs: add support for pin signal phase offset/adjust Arkadiusz Kubalewski
2023-10-02 15:00 ` Jiri Pirko
2023-10-09 22:53 ` Kubalewski, Arkadiusz
2023-09-27 9:24 ` [Intel-wired-lan] [PATCH net-next 2/4] dpll: spec: add support for pin-dpll " Arkadiusz Kubalewski
2023-10-02 14:53 ` Jiri Pirko
2023-10-06 10:29 ` Kubalewski, Arkadiusz
2023-09-27 9:24 ` [Intel-wired-lan] [PATCH net-next 3/4] dpll: netlink/core: " Arkadiusz Kubalewski
2023-09-27 18:09 ` Vadim Fedorenko
2023-10-02 14:32 ` Kubalewski, Arkadiusz
2023-10-02 15:04 ` Jiri Pirko
2023-10-02 15:09 ` Vadim Fedorenko
2023-10-02 23:10 ` Kubalewski, Arkadiusz
2023-10-03 6:27 ` Jiri Pirko
2023-10-03 14:29 ` Kubalewski, Arkadiusz
2023-10-03 17:18 ` Jiri Pirko
2023-10-04 9:13 ` Kubalewski, Arkadiusz
2023-10-02 23:03 ` Kubalewski, Arkadiusz
2023-10-03 6:32 ` Jiri Pirko
2023-10-03 14:29 ` Kubalewski, Arkadiusz
2023-10-03 17:19 ` Jiri Pirko
2023-10-04 9:11 ` Kubalewski, Arkadiusz
2023-09-27 9:24 ` [Intel-wired-lan] [PATCH net-next 4/4] ice: dpll: implement phase related callbacks Arkadiusz Kubalewski
2023-09-27 13:17 ` kernel test robot
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=20230927092435.1565336-1-arkadiusz.kubalewski@intel.com \
--to=arkadiusz.kubalewski@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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