[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250611165415.3c9ed314@kernel.org>
Date: Wed, 11 Jun 2025 16:54:15 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>
Cc: donald.hunter@...il.com, davem@...emloft.net, edumazet@...gle.com,
pabeni@...hat.com, horms@...nel.org, vadim.fedorenko@...ux.dev,
jiri@...nulli.us, anthony.l.nguyen@...el.com, przemyslaw.kitszel@...el.com,
andrew+netdev@...n.ch, aleksandr.loktionov@...el.com, corbet@....net,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
intel-wired-lan@...ts.osuosl.org, linux-rdma@...r.kernel.org,
linux-doc@...r.kernel.org, Milena Olech <milena.olech@...el.com>, Jiri
Pirko <jiri@...dia.com>
Subject: Re: [PATCH net-next v5 1/3] dpll: add reference-sync netlink
attribute
On Tue, 10 Jun 2025 06:04:34 +0200 Arkadiusz Kubalewski wrote:
> +The device may support the Reference SYNC feature, which allows the combination
> +of two inputs into a input pair. In this configuration, clock signals
> +from both inputs are used to synchronize the dpll device. The higher frequency
^^^^
DPLL ?
> +signal is utilized for the loop bandwidth of the DPLL, while the lower frequency
> +signal is used to syntonize the output signal of the DPLL device. This feature
> +enables the provision of a high-quality loop bandwidth signal from an external
> +source.
Looks like there is a conflict between this series and patches sent
by Tony the day before. You'll have to rebase.
--
pw-bot: cr
Powered by blists - more mailing lists