All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Ivan Vecera <ivecera@redhat.com>, netdev@vger.kernel.org
Cc: Eric Dumazet <edumazet@google.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Rob Herring <robh@kernel.org>, Leon Romanovsky <leon@kernel.org>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	linux-rdma@vger.kernel.org,
	Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
	intel-wired-lan@lists.osuosl.org,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
	Jiri Pirko <jiri@resnulli.us>,
	Richard Cochran <richardcochran@gmail.com>,
	Prathosh Satish <Prathosh.Satish@microchip.com>,
	Mark Bloch <mbloch@nvidia.com>,
	linux-kernel@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>,
	Alexander Lobakin <aleksander.lobakin@intel.com>,
	Jonathan Lemon <jonathan.lemon@gmail.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Saeed Mahameed <saeedm@nvidia.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [PATCH net-next 02/12] dpll: Allow associating dpll pin with a firmware node
Date: Fri, 9 Jan 2026 15:46:41 +0000	[thread overview]
Message-ID: <65404ab2-b67d-4138-9aa4-b29fc77ed345@linux.dev> (raw)
In-Reply-To: <20260108182318.20935-3-ivecera@redhat.com>

On 08/01/2026 18:23, Ivan Vecera wrote:
> Extend the DPLL core to support associating a DPLL pin with a firmware
> node. This association is required to allow other subsystems (such as
> network drivers) to locate and request specific DPLL pins defined in
> the Device Tree or ACPI.
> 
> * Add a .fwnode field to the struct dpll_pin
> * Introduce dpll_pin_fwnode_set() helper to allow the provider driver
>    to associate a pin with a fwnode after the pin has been allocated
> * Introduce fwnode_dpll_pin_find() helper to allow consumers to search
>    for a registered DPLL pin using its associated fwnode handle
> * Ensure the fwnode reference is properly released in dpll_pin_put()
> 
> Signed-off-by: Ivan Vecera <ivecera@redhat.com>
> ---
> Changes:
> RFC v2:
> - dpll_pin_fwnode_set() helper to set firmware node without touching
>    dpll_pin_get()

Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>

WARNING: multiple messages have this Message-ID (diff)
From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Ivan Vecera <ivecera@redhat.com>, netdev@vger.kernel.org
Cc: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
	Jiri Pirko <jiri@resnulli.us>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Prathosh Satish <Prathosh.Satish@microchip.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Saeed Mahameed <saeedm@nvidia.com>,
	Leon Romanovsky <leon@kernel.org>,
	Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
	Jonathan Lemon <jonathan.lemon@gmail.com>,
	Richard Cochran <richardcochran@gmail.com>,
	Alexander Lobakin <aleksander.lobakin@intel.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	intel-wired-lan@lists.osuosl.org, linux-rdma@vger.kernel.org,
	Michal Schmidt <mschmidt@redhat.com>,
	Petr Oros <poros@redhat.com>,
	Grzegorz Nitka <grzegorz.nitka@intel.com>
Subject: Re: [PATCH net-next 02/12] dpll: Allow associating dpll pin with a firmware node
Date: Fri, 9 Jan 2026 15:46:41 +0000	[thread overview]
Message-ID: <65404ab2-b67d-4138-9aa4-b29fc77ed345@linux.dev> (raw)
In-Reply-To: <20260108182318.20935-3-ivecera@redhat.com>

On 08/01/2026 18:23, Ivan Vecera wrote:
> Extend the DPLL core to support associating a DPLL pin with a firmware
> node. This association is required to allow other subsystems (such as
> network drivers) to locate and request specific DPLL pins defined in
> the Device Tree or ACPI.
> 
> * Add a .fwnode field to the struct dpll_pin
> * Introduce dpll_pin_fwnode_set() helper to allow the provider driver
>    to associate a pin with a fwnode after the pin has been allocated
> * Introduce fwnode_dpll_pin_find() helper to allow consumers to search
>    for a registered DPLL pin using its associated fwnode handle
> * Ensure the fwnode reference is properly released in dpll_pin_put()
> 
> Signed-off-by: Ivan Vecera <ivecera@redhat.com>
> ---
> Changes:
> RFC v2:
> - dpll_pin_fwnode_set() helper to set firmware node without touching
>    dpll_pin_get()

Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>

  reply	other threads:[~2026-01-09 15:52 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08 18:23 [Intel-wired-lan] [PATCH net-next 00/12] dpll: Core improvements and ice E825-C SyncE support Ivan Vecera
2026-01-08 18:23 ` Ivan Vecera
2026-01-08 18:23 ` [Intel-wired-lan] [PATCH net-next 01/12] dt-bindings: dpll: add common dpll-pin-consumer schema Ivan Vecera
2026-01-08 18:23   ` Ivan Vecera
2026-01-09  9:48   ` [Intel-wired-lan] " Krzysztof Kozlowski
2026-01-09  9:48     ` Krzysztof Kozlowski
2026-01-09 10:22     ` [Intel-wired-lan] " Ivan Vecera
2026-01-09 14:11       ` Ivan Vecera
2026-01-12 16:14         ` Krzysztof Kozlowski
2026-01-12 16:48           ` Ivan Vecera
2026-01-12 18:07             ` Ivan Vecera
2026-01-15 12:01   ` Ivan Vecera
2026-01-15 12:01     ` Ivan Vecera
2026-01-16 15:23     ` [Intel-wired-lan] " Rob Herring
2026-01-16 15:23       ` Rob Herring
2026-01-16 19:00       ` [Intel-wired-lan] " Ivan Vecera
2026-01-16 19:00         ` Ivan Vecera
2026-01-16 23:39         ` [Intel-wired-lan] " Rob Herring
2026-01-16 23:39           ` Rob Herring
2026-01-17 18:21           ` [Intel-wired-lan] " Ivan Vecera
2026-01-17 18:21             ` Ivan Vecera
2026-01-08 18:23 ` [Intel-wired-lan] [PATCH net-next 02/12] dpll: Allow associating dpll pin with a firmware node Ivan Vecera
2026-01-08 18:23   ` Ivan Vecera
2026-01-09 15:46   ` Vadim Fedorenko [this message]
2026-01-09 15:46     ` Vadim Fedorenko
2026-01-08 18:23 ` [Intel-wired-lan] [PATCH net-next 03/12] dpll: Add helpers to find DPLL pin fwnode Ivan Vecera
2026-01-08 18:23   ` Ivan Vecera
2026-01-09  9:55   ` [Intel-wired-lan] " Krzysztof Kozlowski
2026-01-09  9:55     ` Krzysztof Kozlowski
2026-01-09 10:22     ` [Intel-wired-lan] " Ivan Vecera
2026-01-09 10:22       ` Ivan Vecera
2026-01-12 16:16       ` [Intel-wired-lan] " Krzysztof Kozlowski
2026-01-12 16:16         ` Krzysztof Kozlowski
2026-01-12 16:52         ` [Intel-wired-lan] " Ivan Vecera
2026-01-12 16:52           ` Ivan Vecera
2026-01-09 14:19     ` [Intel-wired-lan] " Ivan Vecera
2026-01-09 14:19       ` Ivan Vecera
2026-01-12 16:20       ` [Intel-wired-lan] " Krzysztof Kozlowski
2026-01-12 16:20         ` Krzysztof Kozlowski
2026-01-12 16:55         ` [Intel-wired-lan] " Ivan Vecera
2026-01-12 16:55           ` Ivan Vecera
2026-01-08 18:23 ` [Intel-wired-lan] [PATCH net-next 04/12] dpll: zl3073x: Associate pin with fwnode handle Ivan Vecera
2026-01-08 18:23   ` Ivan Vecera
2026-01-08 18:23 ` [Intel-wired-lan] [PATCH net-next 05/12] dpll: Add notifier chain for dpll events Ivan Vecera
2026-01-08 18:23   ` Ivan Vecera
2026-01-09 16:12   ` [Intel-wired-lan] " Vadim Fedorenko
2026-01-09 16:12     ` Vadim Fedorenko
2026-01-08 18:23 ` [Intel-wired-lan] [PATCH net-next 06/12] dpll: Support dynamic pin index allocation Ivan Vecera
2026-01-08 18:23   ` Ivan Vecera
2026-01-09 23:34   ` [Intel-wired-lan] " kernel test robot
2026-01-12 15:13   ` kernel test robot
2026-01-12 16:56     ` Ivan Vecera
2026-01-12 19:19   ` kernel test robot
2026-01-08 18:23 ` [Intel-wired-lan] [PATCH net-next 07/12] dpll: zl3073x: Add support for mux pin type Ivan Vecera
2026-01-08 18:23   ` Ivan Vecera
2026-01-08 18:23 ` [Intel-wired-lan] [PATCH net-next 08/12] dpll: Enhance and consolidate reference counting logic Ivan Vecera
2026-01-08 18:23   ` Ivan Vecera
2026-01-08 18:23 ` [Intel-wired-lan] [PATCH net-next 09/12] dpll: Prevent duplicate registrations Ivan Vecera
2026-01-08 18:23   ` Ivan Vecera
2026-01-08 18:23 ` [Intel-wired-lan] [PATCH net-next 10/12] dpll: Add reference count tracking support Ivan Vecera
2026-01-08 18:23   ` Ivan Vecera
2026-01-12 16:06   ` [Intel-wired-lan] " kernel test robot
2026-01-08 18:23 ` [Intel-wired-lan] [PATCH net-next 11/12] drivers: Add support for DPLL reference count tracking Ivan Vecera
2026-01-08 18:23   ` Ivan Vecera
2026-01-08 18:23 ` [Intel-wired-lan] [PATCH net-next 12/12] ice: dpll: Support E825-C SyncE and dynamic pin discovery Ivan Vecera
2026-01-08 18:23   ` Ivan Vecera
2026-01-09  6:15   ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-01-09  6:15     ` Loktionov, Aleksandr
2026-01-09 14:47     ` Ivan Vecera

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=65404ab2-b67d-4138-9aa4-b29fc77ed345@linux.dev \
    --to=vadim.fedorenko@linux.dev \
    --cc=Prathosh.Satish@microchip.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=ivecera@redhat.com \
    --cc=jiri@resnulli.us \
    --cc=jonathan.lemon@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=richardcochran@gmail.com \
    --cc=robh@kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.