From: Jiri Pirko <jiri@resnulli.us>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Cc: vadim.fedorenko@linux.dev, corbet@lwn.net,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com,
intel-wired-lan@lists.osuosl.org, kuba@kernel.org,
pabeni@redhat.com, davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH net-next v4 0/5] dpll: add phase-offset and phase-adjust
Date: Tue, 10 Oct 2023 09:44:00 +0200 [thread overview]
Message-ID: <ZSUAwPOy8HAsB4+8@nanopsycho> (raw)
In-Reply-To: <20231009222616.12163-1-arkadiusz.kubalewski@intel.com>
Tue, Oct 10, 2023 at 12:26:11AM CEST, arkadiusz.kubalewski@intel.com wrote:
>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).
>
>v3->v4:
>- do not increase do version of uAPI header as it is not needed (v3 did
> not have this change)
>- fix spelling around commit messages, argument descriptions and docs
>- add missing extack errors on failure set callbacks for pin phase
> adjust and frequency
>- remove ice check if value is already set, now redundant as checked in
> the dpll subsystem
>
>v2->v3:
>- do not increase do version of uAPI header as it is not needed
>
>v1->v2:
>- improve handling for error case of requesting the phase adjust set
>- align handling for error case of frequency set request with the
>approach introduced for phase adjust
>
>
>Arkadiusz Kubalewski (5):
> 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
> dpll: netlink/core: change pin frequency set behavior
I'm fine with the set at is now. Thanks!
set-
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-10-10 7:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 22:26 [Intel-wired-lan] [PATCH net-next v4 0/5] dpll: add phase-offset and phase-adjust Arkadiusz Kubalewski
2023-10-09 22:26 ` [Intel-wired-lan] [PATCH net-next v4 1/5] dpll: docs: add support for pin signal phase offset/adjust Arkadiusz Kubalewski
2023-10-09 22:26 ` [Intel-wired-lan] [PATCH net-next v4 2/5] dpll: spec: add support for pin-dpll " Arkadiusz Kubalewski
2023-10-09 22:26 ` [Intel-wired-lan] [PATCH net-next v4 3/5] dpll: netlink/core: " Arkadiusz Kubalewski
2023-10-09 22:26 ` [Intel-wired-lan] [PATCH net-next v4 4/5] ice: dpll: implement phase related callbacks Arkadiusz Kubalewski
2023-10-09 22:26 ` [Intel-wired-lan] [PATCH net-next v4 5/5] dpll: netlink/core: change pin frequency set behavior Arkadiusz Kubalewski
2023-10-10 7:44 ` Jiri Pirko [this message]
2023-10-10 9:59 ` [Intel-wired-lan] [PATCH net-next v4 0/5] dpll: add phase-offset and phase-adjust Vadim Fedorenko
2023-10-11 2:34 ` Jakub Kicinski
2023-10-11 10:19 ` 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=ZSUAwPOy8HAsB4+8@nanopsycho \
--to=jiri@resnulli.us \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--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