[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y0abOsYjGapUTJHv@nanopsycho>
Date: Wed, 12 Oct 2022 12:47:22 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Vadim Fedorenko <vfedorenko@...ek.ru>
Cc: Jakub Kicinski <kuba@...nel.org>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>,
netdev@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-clk@...r.kernel.org, Vadim Fedorenko <vadfed@...com>
Subject: Re: [RFC PATCH v3 1/6] dpll: Add DPLL framework base functions
Mon, Oct 10, 2022 at 03:17:59AM CEST, vfedorenko@...ek.ru wrote:
>From: Vadim Fedorenko <vadfed@...com>
>
>DPLL framework is used to represent and configure DPLL devices
>in systems. Each device that has DPLL and can configure sources
>and outputs can use this framework.
>
>Signed-off-by: Vadim Fedorenko <vadfed@...com>
>Co-developed-by: Jakub Kicinski <kuba@...nel.org>
>Co-developed-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>
[...]
>+struct dpll_device *dpll_device_alloc(struct dpll_device_ops *ops, const char *name,
>+ int sources_count, int outputs_count, void *priv)
Having constant array of "pins" would not work for SyncE. For example in
mlxsw driver, netdevs can appear and disappear within the device
lifetime (for example port splits, linecard provision). We need to
register/unregister pins dynamically.
[...]
Powered by blists - more mailing lists