public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Jiri Pirko <jiri@resnulli.us>, Jiri Pirko <jiri@nvidia.com>
Cc: 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>,
	Jakub Kicinski <kuba@kernel.org>,
	Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Jonathan Lemon <jonathan.lemon@gmail.com>
Subject: Re: [PATCH net-next 07/11] netdev: expose DPLL pin handle for netdevice
Date: Tue, 1 Aug 2023 14:23:26 +0100	[thread overview]
Message-ID: <4f2e91c7-e2e8-6b3a-fc14-8f44503fb6be@linux.dev> (raw)
In-Reply-To: <20230720091903.297066-8-vadim.fedorenko@linux.dev>

On 20/07/2023 10:18, Vadim Fedorenko wrote:
> From: Jiri Pirko <jiri@nvidia.com>
> 
> In case netdevice represents a SyncE port, the user needs to understand
> the connection between netdevice and associated DPLL pin. There might me
> multiple netdevices pointing to the same pin, in case of VF/SF
> implementation.
> 
> Add a IFLA Netlink attribute to nest the DPLL pin handle, similar to
> how it is implemented for devlink port. Add a struct dpll_pin pointer
> to netdev and protect access to it by RTNL. Expose netdev_dpll_pin_set()
> and netdev_dpll_pin_clear() helpers to the drivers so they can set/clear
> the DPLL pin relationship to netdev.
> 
> Note that during the lifetime of struct dpll_pin the pin handle does not
> change. Therefore it is save to access it lockless. It is drivers
> responsibility to call netdev_dpll_pin_clear() before dpll_pin_put().
> 
> Signed-off-by: Jiri Pirko <jiri@nvidia.com>
> Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
> Signed-off-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
> ---
> RFC v9->v0:
> - rearrange function definition according to usage
> v8->v9:
> - net_device->dpll_pin is only valid if IS_ENABLED(CONFIG_DPLL) fix the
>    code in net/core/rtnetlink.c to respect that.
> - move dpll_msg_add_pin_handle to "dpll: netlink" patch + export the
>    function with this patch
> 
>   drivers/dpll/dpll_netlink.c  | 19 ++++++++++++++++---
>   include/linux/dpll.h         | 20 ++++++++++++++++++++
>   include/linux/netdevice.h    | 20 ++++++++++++++++++++
>   include/uapi/linux/if_link.h |  2 ++
>   net/core/dev.c               | 22 ++++++++++++++++++++++
>   net/core/rtnetlink.c         | 35 +++++++++++++++++++++++++++++++++++
>   6 files changed, 115 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/dpll/dpll_netlink.c b/drivers/dpll/dpll_netlink.c
> index c44dda78737d..e4a9bd767b92 100644
> --- a/drivers/dpll/dpll_netlink.c
> +++ b/drivers/dpll/dpll_netlink.c
> @@ -37,6 +37,18 @@ dpll_msg_add_dev_handle(struct sk_buff *msg, struct dpll_device *dpll)
>   	return 0;
>   }
>   
> +/**
> + * dpll_msg_pin_handle_size - get size of pin handle attribute for given pin
> + * @pin: pin pointer
> + *
> + * Return: byte size of pin handle attribute for given pin.
> + */
> +size_t dpll_msg_pin_handle_size(struct dpll_pin *pin)
> +{
> +	return pin ? nla_total_size(4) : 0; /* DPLL_A_PIN_ID */
> +}
> +EXPORT_SYMBOL_GPL(dpll_msg_pin_handle_size);
> +
>   /**
>    * dpll_msg_add_pin_handle - attach pin handle attribute to a given message
>    * @msg: pointer to sk_buff message to attach a pin handle
> @@ -54,6 +66,7 @@ int dpll_msg_add_pin_handle(struct sk_buff *msg, struct dpll_pin *pin)
>   		return -EMSGSIZE;
>   	return 0;
>   }
> +EXPORT_SYMBOL_GPL(dpll_msg_add_pin_handle);

Jiri, could you please remind me what is the reason to export this 
function? Because I cannot
any usage of this function in drivers.


[....]

  reply	other threads:[~2023-08-01 13:23 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20  9:18 [PATCH net-next 00/11] Create common DPLL configuration API Vadim Fedorenko
2023-07-20  9:18 ` [PATCH net-next 01/11] tools: ynl-gen: fix enum index in _decode_enum(..) Vadim Fedorenko
2023-07-20 13:40   ` Jiri Pirko
2023-07-20 13:58     ` Kubalewski, Arkadiusz
2023-07-20 14:48       ` Vadim Fedorenko
2023-07-20  9:18 ` [PATCH net-next 02/11] tools: ynl-gen: fix parse multi-attr enum attribute Vadim Fedorenko
2023-07-20  9:18 ` [PATCH net-next 03/11] dpll: documentation on DPLL subsystem interface Vadim Fedorenko
2023-07-20 13:47   ` Jiri Pirko
2023-07-20  9:18 ` [PATCH net-next 04/11] dpll: spec: Add Netlink spec in YAML Vadim Fedorenko
2023-07-24 15:52   ` Simon Horman
2023-07-20  9:18 ` [PATCH net-next 05/11] dpll: core: Add DPLL framework base functions Vadim Fedorenko
2023-07-24 15:56   ` Simon Horman
2023-07-20  9:18 ` [PATCH net-next 06/11] dpll: netlink: " Vadim Fedorenko
2023-07-24 16:34   ` Simon Horman
2023-08-01 12:23   ` Jiri Pirko
2023-07-20  9:18 ` [PATCH net-next 07/11] netdev: expose DPLL pin handle for netdevice Vadim Fedorenko
2023-08-01 13:23   ` Vadim Fedorenko [this message]
2023-08-01 15:12     ` Vadim Fedorenko
2023-07-20  9:19 ` [PATCH net-next 08/11] ice: add admin commands to access cgu configuration Vadim Fedorenko
2023-07-24 17:21   ` Simon Horman
2023-07-28 12:46     ` Kubalewski, Arkadiusz
2023-07-20  9:19 ` [PATCH 09/11] ice: implement dpll interface to control cgu Vadim Fedorenko
2023-07-20 14:08   ` Jiri Pirko
2023-07-20 17:31     ` Kubalewski, Arkadiusz
2023-07-21  7:33       ` Jiri Pirko
2023-07-21 11:17         ` Kubalewski, Arkadiusz
2023-07-21 12:02           ` Jiri Pirko
2023-07-21 13:36             ` Kubalewski, Arkadiusz
2023-07-21 15:45               ` Jiri Pirko
2023-07-21 19:48                 ` Kubalewski, Arkadiusz
2023-07-22  6:37                   ` Jiri Pirko
2023-07-24 15:03                     ` Kubalewski, Arkadiusz
2023-07-25  8:03                       ` Jiri Pirko
2023-07-25 14:01                         ` Kubalewski, Arkadiusz
2023-07-26  6:38                           ` Jiri Pirko
2023-07-26 21:11                             ` Kubalewski, Arkadiusz
2023-07-27 10:28                               ` Vadim Fedorenko
2023-07-25 22:49             ` Jakub Kicinski
2023-07-26 15:20               ` Paolo Abeni
2023-07-26 21:10                 ` Kubalewski, Arkadiusz
2023-07-31 12:08                 ` Jiri Pirko
2023-07-26 21:08               ` Kubalewski, Arkadiusz
2023-07-31 12:11               ` Jiri Pirko
2023-07-22  2:08         ` Jakub Kicinski
2023-07-21 11:39   ` Jiri Pirko
2023-07-28 23:03     ` Kubalewski, Arkadiusz
2023-07-31 12:19       ` Jiri Pirko
2023-08-01 14:50         ` Kubalewski, Arkadiusz
2023-08-02  6:57           ` Jiri Pirko
2023-08-02 15:48             ` Kubalewski, Arkadiusz
2023-08-03  8:02               ` Jiri Pirko
2023-08-04  8:58                 ` Kubalewski, Arkadiusz
2023-07-24 17:41   ` Simon Horman
2023-07-24 17:58     ` Vadim Fedorenko
2023-07-28 23:10       ` Kubalewski, Arkadiusz
2023-07-20  9:19 ` [PATCH 10/11] ptp_ocp: implement DPLL ops Vadim Fedorenko
2023-07-21 15:51   ` Jiri Pirko
2023-07-20  9:19 ` [PATCH 11/11] mlx5: Implement SyncE support using DPLL infrastructure Vadim Fedorenko
2023-07-21  7:48 ` [PATCH net-next 00/11] Create common DPLL configuration API Jiri Pirko
2023-07-21 11:14 ` Jiri Pirko
2023-07-21 14:42   ` Vadim Fedorenko
2023-07-21 15:46     ` Jiri Pirko

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=4f2e91c7-e2e8-6b3a-fc14-8f44503fb6be@linux.dev \
    --to=vadim.fedorenko@linux.dev \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=bvanassche@acm.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=michal.michalik@intel.com \
    --cc=milena.olech@intel.com \
    --cc=mschmidt@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=poros@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox