public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Ivan Vecera <ivecera@redhat.com>
Cc: <netdev@vger.kernel.org>, 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>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	"Arkadiusz Kubalewski" <arkadiusz.kubalewski@intel.com>,
	Grzegorz Nitka <grzegorz.nitka@intel.com>,
	Jiri Pirko <jiri@resnulli.us>, Petr Oros <poros@redhat.com>,
	Michal Schmidt <mschmidt@redhat.com>,
	Prathosh Satish <Prathosh.Satish@microchip.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Saeed Mahameed <saeedm@nvidia.com>,
	Leon Romanovsky <leon@kernel.org>,
	"Tariq Toukan" <tariqt@nvidia.com>,
	Mark Bloch <mbloch@nvidia.com>,
	Richard Cochran <richardcochran@gmail.com>,
	Jonathan Lemon <jonathan.lemon@gmail.com>,
	"Simon Horman" <horms@kernel.org>,
	Alexander Lobakin <aleksander.lobakin@intel.com>,
	Willem de Bruijn <willemb@google.com>,
	Stefan Wahren <wahrenst@gmx.net>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<intel-wired-lan@lists.osuosl.org>, <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH RFC net-next 06/13] dpll: Support dynamic pin index allocation
Date: Mon, 15 Dec 2025 15:10:39 +0100	[thread overview]
Message-ID: <7204d8f7-6482-4217-998f-2788d55f4235@intel.com> (raw)
In-Reply-To: <20251211194756.234043-7-ivecera@redhat.com>

On 12/11/25 20:47, Ivan Vecera wrote:
> Allow drivers to register DPLL pins without manually specifying a pin
> index.
> 
> Currently, drivers must provide a unique pin index when calling
> dpll_pin_get(). This works well for hardware-mapped pins but creates
> friction for drivers handling virtual pins or those without a strict
> hardware indexing scheme.

wouldn't it be better to just switch everything to allocated IDs?

> 
> Introduce DPLL_PIN_IDX_UNSPEC (U32_MAX). When a driver passes this
> value as the pin index:
> 1. The core allocates a unique index using an IDA
> 2. The allocated index is mapped to a range starting above `INT_MAX`
> 
> This separation ensures that dynamically allocated indices never collide
> with standard driver-provided hardware indices, which are assumed to be
> within the `0` to `INT_MAX` range. The index is automatically freed when
> the pin is released in dpll_pin_put().
> 
> Signed-off-by: Ivan Vecera <ivecera@redhat.com>
> ---
>   drivers/dpll/dpll_core.c | 48 ++++++++++++++++++++++++++++++++++++++--
>   include/linux/dpll.h     |  2 ++
>   2 files changed, 48 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/dpll/dpll_core.c b/drivers/dpll/dpll_core.c
> index fecc3d97acf5b..79f60e0de27ac 100644
> --- a/drivers/dpll/dpll_core.c
> +++ b/drivers/dpll/dpll_core.c
> @@ -10,6 +10,7 @@
>   
>   #include <linux/device.h>
>   #include <linux/err.h>
> +#include <linux/idr.h>
>   #include <linux/property.h>
>   #include <linux/slab.h>
>   #include <linux/string.h>
> @@ -24,6 +25,7 @@ DEFINE_XARRAY_FLAGS(dpll_device_xa, XA_FLAGS_ALLOC);
>   DEFINE_XARRAY_FLAGS(dpll_pin_xa, XA_FLAGS_ALLOC);
>   
>   static RAW_NOTIFIER_HEAD(dpll_notifier_chain);
> +static DEFINE_IDA(dpll_pin_idx_ida);
>   
>   static u32 dpll_device_xa_id;
>   static u32 dpll_pin_xa_id;
> @@ -468,6 +470,36 @@ void dpll_device_unregister(struct dpll_device *dpll,
>   }
>   EXPORT_SYMBOL_GPL(dpll_device_unregister);
>   
> +static int dpll_pin_idx_alloc(u32 *pin_idx)
> +{
> +	int ret;
> +
> +	if (!pin_idx)
> +		return -EINVAL;
> +
> +	/* Alloc unique number from IDA. Number belongs to <0, INT_MAX> range */
> +	ret = ida_alloc(&dpll_pin_idx_ida, GFP_KERNEL);
> +	if (ret < 0)
> +		return ret;
> +
> +	/* Map the value to dynamic pin index range <INT_MAX+1, U32_MAX> */
> +	*pin_idx = (u32)ret + INT_MAX + 1;
> +
> +	return 0;
> +}
> +
> +static void dpll_pin_idx_free(u32 pin_idx)
> +{
> +	if (pin_idx <= INT_MAX)
> +		return; /* Not a dynamic pin index */
> +
> +	/* Map the index value from dynamic pin index range to IDA range and
> +	 * free it.
> +	 */
> +	pin_idx -= INT_MAX - 1;
> +	ida_free(&dpll_pin_idx_ida, pin_idx);
> +}
> +
>   static void dpll_pin_prop_free(struct dpll_pin_properties *prop)
>   {
>   	kfree(prop->package_label);
> @@ -526,9 +558,18 @@ dpll_pin_alloc(u64 clock_id, u32 pin_idx, struct module *module,
>   	struct dpll_pin *pin;
>   	int ret;
>   
> +	if (pin_idx == DPLL_PIN_IDX_UNSPEC) {
> +		ret = dpll_pin_idx_alloc(&pin_idx);
> +		if (ret)
> +			return ERR_PTR(ret);
> +	} else if (pin_idx > INT_MAX) {
> +		return ERR_PTR(-EINVAL);
> +	}
>   	pin = kzalloc(sizeof(*pin), GFP_KERNEL);
> -	if (!pin)
> -		return ERR_PTR(-ENOMEM);
> +	if (!pin) {
> +		ret = -ENOMEM;
> +		goto err_pin_alloc;
> +	}
>   	pin->pin_idx = pin_idx;
>   	pin->clock_id = clock_id;
>   	pin->module = module;
> @@ -557,6 +598,8 @@ dpll_pin_alloc(u64 clock_id, u32 pin_idx, struct module *module,
>   	dpll_pin_prop_free(&pin->prop);
>   err_pin_prop:
>   	kfree(pin);
> +err_pin_alloc:
> +	dpll_pin_idx_free(pin_idx);
>   	return ERR_PTR(ret);
>   }
>   
> @@ -663,6 +706,7 @@ void dpll_pin_put(struct dpll_pin *pin)
>   		xa_destroy(&pin->ref_sync_pins);
>   		dpll_pin_prop_free(&pin->prop);
>   		fwnode_handle_put(pin->fwnode);
> +		dpll_pin_idx_free(pin->pin_idx);
>   		kfree_rcu(pin, rcu);
>   	}
>   	mutex_unlock(&dpll_lock);
> diff --git a/include/linux/dpll.h b/include/linux/dpll.h
> index 441afb90d2a29..8aa1df38ce563 100644
> --- a/include/linux/dpll.h
> +++ b/include/linux/dpll.h
> @@ -235,6 +235,8 @@ int dpll_device_register(struct dpll_device *dpll, enum dpll_type type,
>   void dpll_device_unregister(struct dpll_device *dpll,
>   			    const struct dpll_device_ops *ops, void *priv);
>   
> +#define DPLL_PIN_IDX_UNSPEC	U32_MAX
> +
>   struct dpll_pin *
>   dpll_pin_get(u64 clock_id, u32 dev_driver_id, struct module *module,
>   	     const struct dpll_pin_properties *prop,


  reply	other threads:[~2025-12-15 14:10 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11 19:47 [PATCH RFC net-next 00/13] dpll: Core improvements and ice E825-C SyncE support Ivan Vecera
2025-12-11 19:47 ` [PATCH RFC net-next 01/13] dt-bindings: net: ethernet-controller: Add DPLL pin properties Ivan Vecera
2025-12-11 19:56   ` Andrew Lunn
2025-12-14 20:41     ` Ivan Vecera
2025-12-17  0:49     ` Rob Herring
2026-01-05 16:23       ` Ivan Vecera
2026-01-07 15:15         ` Rob Herring
2026-01-07 16:23           ` Ivan Vecera
2026-01-07 17:31             ` Andrew Lunn
2026-01-07 19:18               ` Ivan Vecera
2025-12-11 19:47 ` [PATCH RFC net-next 02/13] dpll: Allow registering pin with firmware node Ivan Vecera
2025-12-12 11:25   ` Jiri Pirko
2025-12-14 19:35     ` Ivan Vecera
2025-12-15 13:08       ` Jiri Pirko
2025-12-15 13:51         ` Ivan Vecera
2025-12-15 14:09           ` Jiri Pirko
2025-12-11 19:47 ` [PATCH RFC net-next 03/13] net: eth: Add helpers to find DPLL pin " Ivan Vecera
2025-12-11 19:47 ` [PATCH RFC net-next 04/13] dpll: zl3073x: register pins with fwnode handle Ivan Vecera
2025-12-11 19:47 ` [PATCH RFC net-next 05/13] dpll: Add notifier chain for dpll events Ivan Vecera
2025-12-11 19:47 ` [PATCH RFC net-next 06/13] dpll: Support dynamic pin index allocation Ivan Vecera
2025-12-15 14:10   ` Przemek Kitszel [this message]
2025-12-15 14:43     ` Ivan Vecera
2025-12-11 19:47 ` [PATCH RFC net-next 07/13] dpll: zl3073x: Add support for mux pin type Ivan Vecera
2025-12-11 19:47 ` [PATCH RFC net-next 08/13] dpll: Enhance and consolidate reference counting logic Ivan Vecera
2025-12-11 19:47 ` [PATCH RFC net-next 09/13] dpll: Prevent duplicate registrations Ivan Vecera
2025-12-11 19:47 ` [PATCH RFC net-next 10/13] dpll: Add reference count tracking support Ivan Vecera
2025-12-11 19:47 ` [PATCH RFC net-next 11/13] dpll: zl3073x: Enable reference count tracking Ivan Vecera
2025-12-12 11:11   ` Jiri Pirko
2025-12-11 19:47 ` [PATCH RFC net-next 12/13] ice: dpll: " Ivan Vecera
2025-12-11 19:47 ` [PATCH RFC net-next 13/13] ice: dpll: Support E825-C SyncE and dynamic pin discovery Ivan Vecera
2025-12-12 10:20   ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-12-14 19:30     ` 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=7204d8f7-6482-4217-998f-2788d55f4235@intel.com \
    --to=przemyslaw.kitszel@intel.com \
    --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=grzegorz.nitka@intel.com \
    --cc=horms@kernel.org \
    --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=mschmidt@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=poros@redhat.com \
    --cc=richardcochran@gmail.com \
    --cc=robh@kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.com \
    --cc=vadim.fedorenko@linux.dev \
    --cc=wahrenst@gmx.net \
    --cc=willemb@google.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