From: Vitaly Grinberg <vgrinber@redhat.com>
To: grzegorz.nitka@intel.com
Cc: aleksandr.loktionov@intel.com, anthony.l.nguyen@intel.com,
arkadiusz.kubalewski@intel.com, horms@kernel.org,
intel-wired-lan@lists.osuosl.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pmenzel@molgen.mpg.de, przemyslaw.kitszel@intel.com
Subject: Re:[Intel-wired-lan] [PATCH v5 iwl-next] ice: add support for unmanaged DPLL on E830 NIC
Date: Tue, 16 Dec 2025 16:41:54 +0200 [thread overview]
Message-ID: <20251216144154.15172-1-vgrinber@redhat.com> (raw)
In-Reply-To: <20251120105208.2291441-1-grzegorz.nitka@intel.com>
Will a notification be provided when the lock is re-acquired?
Another concern is the absence of periodical pin notifications. With the E810, users received the active pin notifications every 1 second. However, the unmanaged DPLL appears to lack this functionality. User implementations currently rely on these periodical notifications to derive the overall clock state, metrics and events from the phase offset. It seems that unmanaged DPLL users will be forced to support two distinct types of DPLLs: one that sends periodical pin notifications and one that does not. Crucially, this difference does not appear to be reflected in the device capabilities, meaning users cannot know in advance whether to expect these notifications.
next prev parent reply other threads:[~2025-12-16 14:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 10:52 [PATCH v5 iwl-next] ice: add support for unmanaged DPLL on E830 NIC Grzegorz Nitka
2025-12-16 14:27 ` Vitaly Grinberg
2025-12-16 14:35 ` Vitaly Grinberg
2025-12-16 14:41 ` Vitaly Grinberg [this message]
2026-01-07 21:33 ` Nitka, Grzegorz
2026-01-10 21:29 ` Vitaly Grinberg
2026-01-14 10:23 ` Kubalewski, Arkadiusz
2026-01-14 11:38 ` Vitaly Grinberg
2026-01-14 13:32 ` Kubalewski, Arkadiusz
2026-01-15 8:57 ` Vitaly Grinberg
2026-01-15 15:30 ` Kubalewski, Arkadiusz
2026-01-15 17:25 ` Vitaly Grinberg
2026-01-20 13:14 ` 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=20251216144154.15172-1-vgrinber@redhat.com \
--to=vgrinber@redhat.com \
--cc=aleksandr.loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=grzegorz.nitka@intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=przemyslaw.kitszel@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