From: Jiri Pirko <jiri@resnulli•us>
To: Grzegorz Nitka <grzegorz.nitka@intel•com>
Cc: netdev@vger•kernel.org, linux-kernel@vger•kernel.org,
intel-wired-lan@lists•osuosl.org, poros@redhat•com,
richardcochran@gmail•com, andrew+netdev@lunn•ch,
przemyslaw.kitszel@intel•com, anthony.l.nguyen@intel•com,
Prathosh.Satish@microchip•com, ivecera@redhat•com,
arkadiusz.kubalewski@intel•com, vadim.fedorenko@linux•dev,
donald.hunter@gmail•com, horms@kernel•org, pabeni@redhat•com,
kuba@kernel•org, davem@davemloft•net, edumazet@google•com,
Aleksandr Loktionov <aleksandr.loktionov@intel•com>
Subject: Re: [PATCH v11 net-next 3/8] dpll: extend pin notifier with notification source ID
Date: Tue, 26 May 2026 15:27:19 +0200 [thread overview]
Message-ID: <ahWfsblAd0Cgpe25@FV6GYCPJ69> (raw)
In-Reply-To: <20260526093419.639220-4-grzegorz.nitka@intel.com>
Tue, May 26, 2026 at 11:34:14AM +0200, grzegorz.nitka@intel•com wrote:
>Extend the DPLL pin notification API to include a source identifier
>indicating where the notification originates. This allows notifier
>consumers to distinguish between notifications coming from
>an associated DPLL instance, a parent pin, or the pin itself.
>
>A new field, src_clock_id, is added to struct dpll_pin_notifier_info
>and is passed through all pin-related notification paths. Callers of
>dpll_pin_notify() are updated to provide a meaningful source identifier
>based on their context:
> - pin registration/unregistration uses the DPLL's clock_id,
> - pin-on-pin operations use the parent pin's clock_id,
> - pin changes use the pin's own clock_id.
>
>As introduced in the commit ("dpll: allow registering FW-identified pin
>with a different DPLL"), it is possible to share the same physical pin
>via firmware description (fwnode) with DPLL objects from different
>kernel modules. This means that a given pin can be registered multiple
>times.
>
>Driver such as ICE (E825 devices) rely on this mechanism when listening
>for the event where a shared-fwnode pin appears, while avoiding reacting
>to events triggered by their own registration logic.
>
>This change only extends the notification metadata and does not alter
>existing semantics for drivers that do not use the new field.
>
>Reviewed-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel•com>
>Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel•com>
>Signed-off-by: Grzegorz Nitka <grzegorz.nitka@intel•com>
Reviewed-by: Jiri Pirko <jiri@nvidia•com>
next prev parent reply other threads:[~2026-05-26 13:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 9:34 [PATCH v11 net-next 0/8] dpll/ice: Add generic DPLL type and full TX reference clock control for E825 Grzegorz Nitka
2026-05-26 9:34 ` [PATCH v11 net-next 1/8] dpll: add generic DPLL type Grzegorz Nitka
2026-05-26 13:28 ` Jiri Pirko
2026-05-26 9:34 ` [PATCH v11 net-next 2/8] dpll: allow registering FW-identified pin with a different DPLL Grzegorz Nitka
2026-05-26 9:34 ` [PATCH v11 net-next 3/8] dpll: extend pin notifier with notification source ID Grzegorz Nitka
2026-05-26 13:27 ` Jiri Pirko [this message]
2026-05-26 9:34 ` [PATCH v11 net-next 4/8] dpll: allow fwnode pins to attempt state change without capability bit Grzegorz Nitka
2026-05-26 13:27 ` Jiri Pirko
2026-05-26 9:34 ` [PATCH v11 net-next 5/8] ice: introduce TXC DPLL device and TX ref clock pin framework for E825 Grzegorz Nitka
2026-05-28 8:55 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-05-26 9:34 ` [PATCH v11 net-next 6/8] ice: implement CPI support for E825C Grzegorz Nitka
2026-05-28 8:55 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-05-28 12:24 ` Loktionov, Aleksandr
2026-05-29 14:35 ` Nitka, Grzegorz
2026-05-26 9:34 ` [PATCH v11 net-next 7/8] ice: add Tx reference clock index handling to AN restart command Grzegorz Nitka
2026-05-26 9:34 ` [PATCH v11 net-next 8/8] ice: implement E825 TX ref clock control and TXC hardware sync status Grzegorz Nitka
2026-05-28 12:21 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-05-29 15:08 ` Nitka, Grzegorz
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=ahWfsblAd0Cgpe25@FV6GYCPJ69 \
--to=jiri@resnulli$(echo .)us \
--cc=Prathosh.Satish@microchip$(echo .)com \
--cc=aleksandr.loktionov@intel$(echo .)com \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=anthony.l.nguyen@intel$(echo .)com \
--cc=arkadiusz.kubalewski@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=donald.hunter@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=grzegorz.nitka@intel$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=intel-wired-lan@lists$(echo .)osuosl.org \
--cc=ivecera@redhat$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=poros@redhat$(echo .)com \
--cc=przemyslaw.kitszel@intel$(echo .)com \
--cc=richardcochran@gmail$(echo .)com \
--cc=vadim.fedorenko@linux$(echo .)dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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