From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Jiri Pirko <jiri@resnulli.us>,
Bart Van Assche <bvanassche@acm.org>,
netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
linux-arm-kernel@lists.infradead.org,
Jiri Pirko <jiri@nvidia.com>,
Jonathan Lemon <jonathan.lemon@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-clk@vger.kernel.org, Milena Olech <milena.olech@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next v4 3/9] dpll: core: Add DPLL framework base functions
Date: Tue, 15 Aug 2023 19:20:31 +0100 [thread overview]
Message-ID: <ef2eca98-4fcc-b448-fecb-38695238f87b@linux.dev> (raw)
In-Reply-To: <20230814201709.655a24e2@kernel.org>
On 15/08/2023 04:17, Jakub Kicinski wrote:
> On Fri, 11 Aug 2023 21:03:34 +0100 Vadim Fedorenko wrote:
>> DPLL framework is used to represent and configure DPLL devices
>> in systems. Each device that has DPLL and can configure inputs
>> and outputs can use this framework.
>>
>> Implement core framework functions for further interactions
>> with device drivers implementing dpll subsystem, as well as for
>> interactions of DPLL netlink framework part with the subsystem
>> itself.
>
>> +static struct dpll_device *
>> +dpll_device_alloc(const u64 clock_id, u32 device_idx, struct module *module)
>> +{
>> + struct dpll_device *dpll;
>> + int ret;
>> +
>> + dpll = kzalloc(sizeof(*dpll), GFP_KERNEL);
>> + if (!dpll)
>> + return ERR_PTR(-ENOMEM);
>> + refcount_set(&dpll->refcount, 1);
>> + INIT_LIST_HEAD(&dpll->registration_list);
>> + dpll->device_idx = device_idx;
>> + dpll->clock_id = clock_id;
>> + dpll->module = module;
>> + ret = xa_alloc(&dpll_device_xa, &dpll->id, dpll, xa_limit_16b,
>> + GFP_KERNEL);
>
> Why only 16b and why not _cyclic?
>
I cannot image systems with more than 65k of DPLL devices. We don't
store any id's of last used DPLL device, so there is no easy way to
restart the search from the last point. And it's not a hot path to
optimize it.
>> +/**
>> + * dpll_device_register - register the dpll device in the subsystem
>> + * @dpll: pointer to a dpll
>> + * @type: type of a dpll
>> + * @ops: ops for a dpll device
>> + * @priv: pointer to private information of owner
>> + *
>> + * Make dpll device available for user space.
>> + *
>> + * Context: Acquires a lock (dpll_lock)
>> + * Return:
>> + * * 0 on success
>> + * * negative - error value
>> + */
>> +int dpll_device_register(struct dpll_device *dpll, enum dpll_type type,
>> + const struct dpll_device_ops *ops, void *priv)
>> +{
>> + struct dpll_device_registration *reg;
>> + bool first_registration = false;
>> +
>> + if (WARN_ON(!ops))
>> + return -EINVAL;
>> + if (WARN_ON(!ops->mode_get))
>> + return -EINVAL;
>> + if (WARN_ON(!ops->lock_status_get))
>> + return -EINVAL;
>> + if (WARN_ON(type < DPLL_TYPE_PPS || type > DPLL_TYPE_MAX))
>> + return -EINVAL;
>> +
>> + mutex_lock(&dpll_lock);
>> + reg = dpll_device_registration_find(dpll, ops, priv);
>> + if (reg) {
>> + mutex_unlock(&dpll_lock);
>> + return -EEXIST;
>> + }
>> +
>> + reg = kzalloc(sizeof(*reg), GFP_KERNEL);
>> + if (!reg) {
>> + mutex_unlock(&dpll_lock);
>> + return -ENOMEM;
>> + }
>> + reg->ops = ops;
>> + reg->priv = priv;
>> + dpll->type = type;
>> + first_registration = list_empty(&dpll->registration_list);
>> + list_add_tail(®->list, &dpll->registration_list);
>> + if (!first_registration) {
>> + mutex_unlock(&dpll_lock);
>> + return 0;
>> + }
>> +
>> + xa_set_mark(&dpll_device_xa, dpll->id, DPLL_REGISTERED);
>> + mutex_unlock(&dpll_lock);
>> +
>> + return 0;
>> +}
>> +EXPORT_SYMBOL_GPL(dpll_device_register);
>
> Is the registration flow documented? It's a bit atypical so we should
> write some pseudocode somewhere.
>
Yeah, I'll add it and point to the drivers as examples.
>> +/**
>> + * dpll_device_unregister - unregister dpll device
>> + * @dpll: registered dpll pointer
>> + * @ops: ops for a dpll device
>> + * @priv: pointer to private information of owner
>> + *
>> + * Unregister device, make it unavailable for userspace.
>> + * Note: It does not free the memory
>> + * Context: Acquires a lock (dpll_lock)
>> + */
>> +void dpll_device_unregister(struct dpll_device *dpll,
>> + const struct dpll_device_ops *ops, void *priv)
>> +{
>> + struct dpll_device_registration *reg;
>> +
>> + mutex_lock(&dpll_lock);
>> + ASSERT_DPLL_REGISTERED(dpll);
>> + reg = dpll_device_registration_find(dpll, ops, priv);
>> + if (WARN_ON(!reg)) {
>> + mutex_unlock(&dpll_lock);
>> + return;
>> + }
>> + list_del(®->list);
>> + kfree(reg);
>> +
>> + if (!list_empty(&dpll->registration_list)) {
>> + mutex_unlock(&dpll_lock);
>> + return;
>> + }
>> + xa_clear_mark(&dpll_device_xa, dpll->id, DPLL_REGISTERED);
>> + mutex_unlock(&dpll_lock);
>> +}
>> +EXPORT_SYMBOL_GPL(dpll_device_unregister);
>
>> +/**
>> + * struct dpll_pin - structure for a dpll pin
>> + * @id: unique id number for pin given by dpll subsystem
>> + * @pin_idx: index of a pin given by dev driver
>> + * @clock_id: clock_id of creator
>> + * @module: module of creator
>> + * @dpll_refs: hold referencees to dplls pin was registered with
>> + * @parent_refs: hold references to parent pins pin was registered with
>> + * @prop: pointer to pin properties given by registerer
>> + * @rclk_dev_name: holds name of device when pin can recover clock from it
>> + * @refcount: refcount
>> + **/
>> +struct dpll_pin {
>> + u32 id;
>> + u32 pin_idx;
>> + u64 clock_id;
>> + struct module *module;
>> + struct xarray dpll_refs;
>> + struct xarray parent_refs;
>> + const struct dpll_pin_properties *prop;
>> + char *rclk_dev_name;
>
> Where is rclk_dev_name filled in?
As Jiri said - left over, will remove it.
>> +struct dpll_pin_ops {
>> + int (*frequency_set)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + const u64 frequency,
>> + struct netlink_ext_ack *extack);
>> + int (*frequency_get)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + u64 *frequency, struct netlink_ext_ack *extack);
>> + int (*direction_set)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + const enum dpll_pin_direction direction,
>> + struct netlink_ext_ack *extack);
>> + int (*direction_get)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + enum dpll_pin_direction *direction,
>> + struct netlink_ext_ack *extack);
>> + int (*state_on_pin_get)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_pin *parent_pin,
>> + void *parent_pin_priv,
>> + enum dpll_pin_state *state,
>> + struct netlink_ext_ack *extack);
>> + int (*state_on_dpll_get)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll,
>> + void *dpll_priv, enum dpll_pin_state *state,
>> + struct netlink_ext_ack *extack);
>> + int (*state_on_pin_set)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_pin *parent_pin,
>> + void *parent_pin_priv,
>> + const enum dpll_pin_state state,
>> + struct netlink_ext_ack *extack);
>> + int (*state_on_dpll_set)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll,
>> + void *dpll_priv,
>> + const enum dpll_pin_state state,
>> + struct netlink_ext_ack *extack);
>> + int (*prio_get)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + u32 *prio, struct netlink_ext_ack *extack);
>> + int (*prio_set)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + const u32 prio, struct netlink_ext_ack *extack);
>> +};
>
> The ops need a kdoc
Ok, will add it.
>
>> +struct dpll_device
>> +*dpll_device_get(u64 clock_id, u32 dev_driver_id, struct module *module);
>
> nit: * is part of the type, it goes on the previous line
Fixed, thanks!
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Jiri Pirko <jiri@resnulli.us>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jonathan Lemon <jonathan.lemon@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
Milena Olech <milena.olech@intel.com>,
Michal Michalik <michal.michalik@intel.com>,
linux-arm-kernel@lists.infradead.org, poros@redhat.com,
mschmidt@redhat.com, netdev@vger.kernel.org,
linux-clk@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>,
intel-wired-lan@lists.osuosl.org, Jiri Pirko <jiri@nvidia.com>
Subject: Re: [PATCH net-next v4 3/9] dpll: core: Add DPLL framework base functions
Date: Tue, 15 Aug 2023 19:20:31 +0100 [thread overview]
Message-ID: <ef2eca98-4fcc-b448-fecb-38695238f87b@linux.dev> (raw)
In-Reply-To: <20230814201709.655a24e2@kernel.org>
On 15/08/2023 04:17, Jakub Kicinski wrote:
> On Fri, 11 Aug 2023 21:03:34 +0100 Vadim Fedorenko wrote:
>> DPLL framework is used to represent and configure DPLL devices
>> in systems. Each device that has DPLL and can configure inputs
>> and outputs can use this framework.
>>
>> Implement core framework functions for further interactions
>> with device drivers implementing dpll subsystem, as well as for
>> interactions of DPLL netlink framework part with the subsystem
>> itself.
>
>> +static struct dpll_device *
>> +dpll_device_alloc(const u64 clock_id, u32 device_idx, struct module *module)
>> +{
>> + struct dpll_device *dpll;
>> + int ret;
>> +
>> + dpll = kzalloc(sizeof(*dpll), GFP_KERNEL);
>> + if (!dpll)
>> + return ERR_PTR(-ENOMEM);
>> + refcount_set(&dpll->refcount, 1);
>> + INIT_LIST_HEAD(&dpll->registration_list);
>> + dpll->device_idx = device_idx;
>> + dpll->clock_id = clock_id;
>> + dpll->module = module;
>> + ret = xa_alloc(&dpll_device_xa, &dpll->id, dpll, xa_limit_16b,
>> + GFP_KERNEL);
>
> Why only 16b and why not _cyclic?
>
I cannot image systems with more than 65k of DPLL devices. We don't
store any id's of last used DPLL device, so there is no easy way to
restart the search from the last point. And it's not a hot path to
optimize it.
>> +/**
>> + * dpll_device_register - register the dpll device in the subsystem
>> + * @dpll: pointer to a dpll
>> + * @type: type of a dpll
>> + * @ops: ops for a dpll device
>> + * @priv: pointer to private information of owner
>> + *
>> + * Make dpll device available for user space.
>> + *
>> + * Context: Acquires a lock (dpll_lock)
>> + * Return:
>> + * * 0 on success
>> + * * negative - error value
>> + */
>> +int dpll_device_register(struct dpll_device *dpll, enum dpll_type type,
>> + const struct dpll_device_ops *ops, void *priv)
>> +{
>> + struct dpll_device_registration *reg;
>> + bool first_registration = false;
>> +
>> + if (WARN_ON(!ops))
>> + return -EINVAL;
>> + if (WARN_ON(!ops->mode_get))
>> + return -EINVAL;
>> + if (WARN_ON(!ops->lock_status_get))
>> + return -EINVAL;
>> + if (WARN_ON(type < DPLL_TYPE_PPS || type > DPLL_TYPE_MAX))
>> + return -EINVAL;
>> +
>> + mutex_lock(&dpll_lock);
>> + reg = dpll_device_registration_find(dpll, ops, priv);
>> + if (reg) {
>> + mutex_unlock(&dpll_lock);
>> + return -EEXIST;
>> + }
>> +
>> + reg = kzalloc(sizeof(*reg), GFP_KERNEL);
>> + if (!reg) {
>> + mutex_unlock(&dpll_lock);
>> + return -ENOMEM;
>> + }
>> + reg->ops = ops;
>> + reg->priv = priv;
>> + dpll->type = type;
>> + first_registration = list_empty(&dpll->registration_list);
>> + list_add_tail(®->list, &dpll->registration_list);
>> + if (!first_registration) {
>> + mutex_unlock(&dpll_lock);
>> + return 0;
>> + }
>> +
>> + xa_set_mark(&dpll_device_xa, dpll->id, DPLL_REGISTERED);
>> + mutex_unlock(&dpll_lock);
>> +
>> + return 0;
>> +}
>> +EXPORT_SYMBOL_GPL(dpll_device_register);
>
> Is the registration flow documented? It's a bit atypical so we should
> write some pseudocode somewhere.
>
Yeah, I'll add it and point to the drivers as examples.
>> +/**
>> + * dpll_device_unregister - unregister dpll device
>> + * @dpll: registered dpll pointer
>> + * @ops: ops for a dpll device
>> + * @priv: pointer to private information of owner
>> + *
>> + * Unregister device, make it unavailable for userspace.
>> + * Note: It does not free the memory
>> + * Context: Acquires a lock (dpll_lock)
>> + */
>> +void dpll_device_unregister(struct dpll_device *dpll,
>> + const struct dpll_device_ops *ops, void *priv)
>> +{
>> + struct dpll_device_registration *reg;
>> +
>> + mutex_lock(&dpll_lock);
>> + ASSERT_DPLL_REGISTERED(dpll);
>> + reg = dpll_device_registration_find(dpll, ops, priv);
>> + if (WARN_ON(!reg)) {
>> + mutex_unlock(&dpll_lock);
>> + return;
>> + }
>> + list_del(®->list);
>> + kfree(reg);
>> +
>> + if (!list_empty(&dpll->registration_list)) {
>> + mutex_unlock(&dpll_lock);
>> + return;
>> + }
>> + xa_clear_mark(&dpll_device_xa, dpll->id, DPLL_REGISTERED);
>> + mutex_unlock(&dpll_lock);
>> +}
>> +EXPORT_SYMBOL_GPL(dpll_device_unregister);
>
>> +/**
>> + * struct dpll_pin - structure for a dpll pin
>> + * @id: unique id number for pin given by dpll subsystem
>> + * @pin_idx: index of a pin given by dev driver
>> + * @clock_id: clock_id of creator
>> + * @module: module of creator
>> + * @dpll_refs: hold referencees to dplls pin was registered with
>> + * @parent_refs: hold references to parent pins pin was registered with
>> + * @prop: pointer to pin properties given by registerer
>> + * @rclk_dev_name: holds name of device when pin can recover clock from it
>> + * @refcount: refcount
>> + **/
>> +struct dpll_pin {
>> + u32 id;
>> + u32 pin_idx;
>> + u64 clock_id;
>> + struct module *module;
>> + struct xarray dpll_refs;
>> + struct xarray parent_refs;
>> + const struct dpll_pin_properties *prop;
>> + char *rclk_dev_name;
>
> Where is rclk_dev_name filled in?
As Jiri said - left over, will remove it.
>> +struct dpll_pin_ops {
>> + int (*frequency_set)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + const u64 frequency,
>> + struct netlink_ext_ack *extack);
>> + int (*frequency_get)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + u64 *frequency, struct netlink_ext_ack *extack);
>> + int (*direction_set)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + const enum dpll_pin_direction direction,
>> + struct netlink_ext_ack *extack);
>> + int (*direction_get)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + enum dpll_pin_direction *direction,
>> + struct netlink_ext_ack *extack);
>> + int (*state_on_pin_get)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_pin *parent_pin,
>> + void *parent_pin_priv,
>> + enum dpll_pin_state *state,
>> + struct netlink_ext_ack *extack);
>> + int (*state_on_dpll_get)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll,
>> + void *dpll_priv, enum dpll_pin_state *state,
>> + struct netlink_ext_ack *extack);
>> + int (*state_on_pin_set)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_pin *parent_pin,
>> + void *parent_pin_priv,
>> + const enum dpll_pin_state state,
>> + struct netlink_ext_ack *extack);
>> + int (*state_on_dpll_set)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll,
>> + void *dpll_priv,
>> + const enum dpll_pin_state state,
>> + struct netlink_ext_ack *extack);
>> + int (*prio_get)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + u32 *prio, struct netlink_ext_ack *extack);
>> + int (*prio_set)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + const u32 prio, struct netlink_ext_ack *extack);
>> +};
>
> The ops need a kdoc
Ok, will add it.
>
>> +struct dpll_device
>> +*dpll_device_get(u64 clock_id, u32 dev_driver_id, struct module *module);
>
> nit: * is part of the type, it goes on the previous line
Fixed, thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Jiri Pirko <jiri@resnulli.us>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jonathan Lemon <jonathan.lemon@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
Milena Olech <milena.olech@intel.com>,
Michal Michalik <michal.michalik@intel.com>,
linux-arm-kernel@lists.infradead.org, poros@redhat.com,
mschmidt@redhat.com, netdev@vger.kernel.org,
linux-clk@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>,
intel-wired-lan@lists.osuosl.org, Jiri Pirko <jiri@nvidia.com>
Subject: Re: [PATCH net-next v4 3/9] dpll: core: Add DPLL framework base functions
Date: Tue, 15 Aug 2023 19:20:31 +0100 [thread overview]
Message-ID: <ef2eca98-4fcc-b448-fecb-38695238f87b@linux.dev> (raw)
In-Reply-To: <20230814201709.655a24e2@kernel.org>
On 15/08/2023 04:17, Jakub Kicinski wrote:
> On Fri, 11 Aug 2023 21:03:34 +0100 Vadim Fedorenko wrote:
>> DPLL framework is used to represent and configure DPLL devices
>> in systems. Each device that has DPLL and can configure inputs
>> and outputs can use this framework.
>>
>> Implement core framework functions for further interactions
>> with device drivers implementing dpll subsystem, as well as for
>> interactions of DPLL netlink framework part with the subsystem
>> itself.
>
>> +static struct dpll_device *
>> +dpll_device_alloc(const u64 clock_id, u32 device_idx, struct module *module)
>> +{
>> + struct dpll_device *dpll;
>> + int ret;
>> +
>> + dpll = kzalloc(sizeof(*dpll), GFP_KERNEL);
>> + if (!dpll)
>> + return ERR_PTR(-ENOMEM);
>> + refcount_set(&dpll->refcount, 1);
>> + INIT_LIST_HEAD(&dpll->registration_list);
>> + dpll->device_idx = device_idx;
>> + dpll->clock_id = clock_id;
>> + dpll->module = module;
>> + ret = xa_alloc(&dpll_device_xa, &dpll->id, dpll, xa_limit_16b,
>> + GFP_KERNEL);
>
> Why only 16b and why not _cyclic?
>
I cannot image systems with more than 65k of DPLL devices. We don't
store any id's of last used DPLL device, so there is no easy way to
restart the search from the last point. And it's not a hot path to
optimize it.
>> +/**
>> + * dpll_device_register - register the dpll device in the subsystem
>> + * @dpll: pointer to a dpll
>> + * @type: type of a dpll
>> + * @ops: ops for a dpll device
>> + * @priv: pointer to private information of owner
>> + *
>> + * Make dpll device available for user space.
>> + *
>> + * Context: Acquires a lock (dpll_lock)
>> + * Return:
>> + * * 0 on success
>> + * * negative - error value
>> + */
>> +int dpll_device_register(struct dpll_device *dpll, enum dpll_type type,
>> + const struct dpll_device_ops *ops, void *priv)
>> +{
>> + struct dpll_device_registration *reg;
>> + bool first_registration = false;
>> +
>> + if (WARN_ON(!ops))
>> + return -EINVAL;
>> + if (WARN_ON(!ops->mode_get))
>> + return -EINVAL;
>> + if (WARN_ON(!ops->lock_status_get))
>> + return -EINVAL;
>> + if (WARN_ON(type < DPLL_TYPE_PPS || type > DPLL_TYPE_MAX))
>> + return -EINVAL;
>> +
>> + mutex_lock(&dpll_lock);
>> + reg = dpll_device_registration_find(dpll, ops, priv);
>> + if (reg) {
>> + mutex_unlock(&dpll_lock);
>> + return -EEXIST;
>> + }
>> +
>> + reg = kzalloc(sizeof(*reg), GFP_KERNEL);
>> + if (!reg) {
>> + mutex_unlock(&dpll_lock);
>> + return -ENOMEM;
>> + }
>> + reg->ops = ops;
>> + reg->priv = priv;
>> + dpll->type = type;
>> + first_registration = list_empty(&dpll->registration_list);
>> + list_add_tail(®->list, &dpll->registration_list);
>> + if (!first_registration) {
>> + mutex_unlock(&dpll_lock);
>> + return 0;
>> + }
>> +
>> + xa_set_mark(&dpll_device_xa, dpll->id, DPLL_REGISTERED);
>> + mutex_unlock(&dpll_lock);
>> +
>> + return 0;
>> +}
>> +EXPORT_SYMBOL_GPL(dpll_device_register);
>
> Is the registration flow documented? It's a bit atypical so we should
> write some pseudocode somewhere.
>
Yeah, I'll add it and point to the drivers as examples.
>> +/**
>> + * dpll_device_unregister - unregister dpll device
>> + * @dpll: registered dpll pointer
>> + * @ops: ops for a dpll device
>> + * @priv: pointer to private information of owner
>> + *
>> + * Unregister device, make it unavailable for userspace.
>> + * Note: It does not free the memory
>> + * Context: Acquires a lock (dpll_lock)
>> + */
>> +void dpll_device_unregister(struct dpll_device *dpll,
>> + const struct dpll_device_ops *ops, void *priv)
>> +{
>> + struct dpll_device_registration *reg;
>> +
>> + mutex_lock(&dpll_lock);
>> + ASSERT_DPLL_REGISTERED(dpll);
>> + reg = dpll_device_registration_find(dpll, ops, priv);
>> + if (WARN_ON(!reg)) {
>> + mutex_unlock(&dpll_lock);
>> + return;
>> + }
>> + list_del(®->list);
>> + kfree(reg);
>> +
>> + if (!list_empty(&dpll->registration_list)) {
>> + mutex_unlock(&dpll_lock);
>> + return;
>> + }
>> + xa_clear_mark(&dpll_device_xa, dpll->id, DPLL_REGISTERED);
>> + mutex_unlock(&dpll_lock);
>> +}
>> +EXPORT_SYMBOL_GPL(dpll_device_unregister);
>
>> +/**
>> + * struct dpll_pin - structure for a dpll pin
>> + * @id: unique id number for pin given by dpll subsystem
>> + * @pin_idx: index of a pin given by dev driver
>> + * @clock_id: clock_id of creator
>> + * @module: module of creator
>> + * @dpll_refs: hold referencees to dplls pin was registered with
>> + * @parent_refs: hold references to parent pins pin was registered with
>> + * @prop: pointer to pin properties given by registerer
>> + * @rclk_dev_name: holds name of device when pin can recover clock from it
>> + * @refcount: refcount
>> + **/
>> +struct dpll_pin {
>> + u32 id;
>> + u32 pin_idx;
>> + u64 clock_id;
>> + struct module *module;
>> + struct xarray dpll_refs;
>> + struct xarray parent_refs;
>> + const struct dpll_pin_properties *prop;
>> + char *rclk_dev_name;
>
> Where is rclk_dev_name filled in?
As Jiri said - left over, will remove it.
>> +struct dpll_pin_ops {
>> + int (*frequency_set)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + const u64 frequency,
>> + struct netlink_ext_ack *extack);
>> + int (*frequency_get)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + u64 *frequency, struct netlink_ext_ack *extack);
>> + int (*direction_set)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + const enum dpll_pin_direction direction,
>> + struct netlink_ext_ack *extack);
>> + int (*direction_get)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + enum dpll_pin_direction *direction,
>> + struct netlink_ext_ack *extack);
>> + int (*state_on_pin_get)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_pin *parent_pin,
>> + void *parent_pin_priv,
>> + enum dpll_pin_state *state,
>> + struct netlink_ext_ack *extack);
>> + int (*state_on_dpll_get)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll,
>> + void *dpll_priv, enum dpll_pin_state *state,
>> + struct netlink_ext_ack *extack);
>> + int (*state_on_pin_set)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_pin *parent_pin,
>> + void *parent_pin_priv,
>> + const enum dpll_pin_state state,
>> + struct netlink_ext_ack *extack);
>> + int (*state_on_dpll_set)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll,
>> + void *dpll_priv,
>> + const enum dpll_pin_state state,
>> + struct netlink_ext_ack *extack);
>> + int (*prio_get)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + u32 *prio, struct netlink_ext_ack *extack);
>> + int (*prio_set)(const struct dpll_pin *pin, void *pin_priv,
>> + const struct dpll_device *dpll, void *dpll_priv,
>> + const u32 prio, struct netlink_ext_ack *extack);
>> +};
>
> The ops need a kdoc
Ok, will add it.
>
>> +struct dpll_device
>> +*dpll_device_get(u64 clock_id, u32 dev_driver_id, struct module *module);
>
> nit: * is part of the type, it goes on the previous line
Fixed, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-15 18:20 UTC|newest]
Thread overview: 111+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 20:03 [Intel-wired-lan] [PATCH net-next v4 0/9] Create common DPLL configuration API Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 1/9] dpll: documentation on DPLL subsystem interface Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-15 2:52 ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15 2:52 ` Jakub Kicinski
2023-08-15 2:52 ` Jakub Kicinski
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 2/9] dpll: spec: Add Netlink spec in YAML Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-15 2:43 ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15 2:43 ` Jakub Kicinski
2023-08-15 2:43 ` Jakub Kicinski
2023-08-17 18:40 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-08-17 18:40 ` Kubalewski, Arkadiusz
2023-08-17 18:40 ` Kubalewski, Arkadiusz
2023-08-17 23:36 ` [Intel-wired-lan] " Jakub Kicinski
2023-08-17 23:36 ` Jakub Kicinski
2023-08-17 23:36 ` Jakub Kicinski
2023-08-18 7:23 ` [Intel-wired-lan] " Jiri Pirko
2023-08-18 7:23 ` Jiri Pirko
2023-08-18 7:23 ` Jiri Pirko
2023-08-21 10:15 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-08-21 10:15 ` Kubalewski, Arkadiusz
2023-08-21 10:15 ` Kubalewski, Arkadiusz
2023-08-22 16:54 ` [Intel-wired-lan] " Jakub Kicinski
2023-08-22 16:54 ` Jakub Kicinski
2023-08-22 16:54 ` Jakub Kicinski
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 3/9] dpll: core: Add DPLL framework base functions Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-15 3:17 ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15 3:17 ` Jakub Kicinski
2023-08-15 3:17 ` Jakub Kicinski
2023-08-15 6:00 ` [Intel-wired-lan] " Jiri Pirko
2023-08-15 6:00 ` Jiri Pirko
2023-08-15 6:00 ` Jiri Pirko
2023-08-15 18:20 ` Vadim Fedorenko [this message]
2023-08-15 18:20 ` Vadim Fedorenko
2023-08-15 18:20 ` Vadim Fedorenko
2023-08-15 18:28 ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15 18:28 ` Jakub Kicinski
2023-08-15 18:28 ` Jakub Kicinski
2023-08-15 18:38 ` [Intel-wired-lan] " Vadim Fedorenko
2023-08-15 18:38 ` Vadim Fedorenko
2023-08-15 18:38 ` Vadim Fedorenko
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 4/9] dpll: netlink: " Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-15 3:23 ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15 3:23 ` Jakub Kicinski
2023-08-15 3:23 ` Jakub Kicinski
2023-08-15 3:24 ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15 3:24 ` Jakub Kicinski
2023-08-15 3:24 ` Jakub Kicinski
2023-08-15 15:18 ` [Intel-wired-lan] " Vadim Fedorenko
2023-08-15 15:18 ` Vadim Fedorenko
2023-08-15 15:18 ` Vadim Fedorenko
2023-08-15 16:55 ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15 16:55 ` Jakub Kicinski
2023-08-15 16:55 ` Jakub Kicinski
2023-08-15 18:25 ` [Intel-wired-lan] " Vadim Fedorenko
2023-08-15 18:25 ` Vadim Fedorenko
2023-08-15 18:25 ` Vadim Fedorenko
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 5/9] netdev: expose DPLL pin handle for netdevice Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 6/9] ice: add admin commands to access cgu configuration Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 7/9] ice: implement dpll interface to control cgu Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-12 6:19 ` [Intel-wired-lan] " Jiri Pirko
2023-08-12 6:19 ` Jiri Pirko
2023-08-12 6:19 ` Jiri Pirko
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 8/9] ptp_ocp: implement DPLL ops Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-11 20:03 ` [Intel-wired-lan] [PATCH net-next v4 9/9] mlx5: Implement SyncE support using DPLL infrastructure Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-11 20:03 ` Vadim Fedorenko
2023-08-12 6:22 ` [Intel-wired-lan] [PATCH net-next v4 0/9] Create common DPLL configuration API Jiri Pirko
2023-08-12 6:22 ` Jiri Pirko
2023-08-12 6:22 ` Jiri Pirko
2023-08-12 11:20 ` [Intel-wired-lan] " Vadim Fedorenko
2023-08-12 11:20 ` Vadim Fedorenko
2023-08-12 11:20 ` Vadim Fedorenko
2023-08-15 2:45 ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15 2:45 ` Jakub Kicinski
2023-08-15 2:45 ` Jakub Kicinski
2023-08-15 11:36 ` [Intel-wired-lan] " Vadim Fedorenko
2023-08-15 11:36 ` Vadim Fedorenko
2023-08-15 11:36 ` Vadim Fedorenko
2023-08-15 11:52 ` [Intel-wired-lan] " Jiri Pirko
2023-08-15 11:52 ` Jiri Pirko
2023-08-15 11:52 ` Jiri Pirko
2023-08-15 14:32 ` [Intel-wired-lan] " Vadim Fedorenko
2023-08-15 14:32 ` Vadim Fedorenko
2023-08-15 14:32 ` Vadim Fedorenko
2023-08-15 17:02 ` [Intel-wired-lan] " Jakub Kicinski
2023-08-15 17:02 ` Jakub Kicinski
2023-08-15 17:02 ` Jakub Kicinski
2023-08-18 10:15 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-08-18 10:15 ` Kubalewski, Arkadiusz
2023-08-18 10:15 ` Kubalewski, Arkadiusz
2023-08-18 21:03 ` [Intel-wired-lan] " Jakub Kicinski
2023-08-18 21:03 ` Jakub Kicinski
2023-08-18 21:03 ` Jakub Kicinski
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=ef2eca98-4fcc-b448-fecb-38695238f87b@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=bvanassche@acm.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jiri@nvidia.com \
--cc=jiri@resnulli.us \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=milena.olech@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.