netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Vecera <ivecera@redhat.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org,
	Prathosh Satish <Prathosh.Satish@microchip.com>,
	Jiri Pirko <jiri@resnulli.us>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] dpll: zl3073x: Allow to use custom phase measure averaging factor
Date: Wed, 10 Sep 2025 18:50:47 +0200	[thread overview]
Message-ID: <0817610a-e3dd-427e-b0ad-c2d503bb8a4f@redhat.com> (raw)
In-Reply-To: <acfc8c63-4434-4738-84a9-00360e70c773@lunn.ch>

On 10. 09. 25 6:13 odp., Andrew Lunn wrote:
> On Wed, Sep 10, 2025 at 12:32:21PM +0200, Ivan Vecera wrote:
>> The DPLL phase measurement block uses an exponential moving average,
>> calculated using the following equation:
>>
>>                         2^N - 1                1
>> curr_avg = prev_avg * --------- + new_val * -----
>>                           2^N                 2^N
>>
>> Where curr_avg is phase offset reported by the firmware to the driver,
>> prev_avg is previous averaged value and new_val is currently measured
>> value for particular reference.
>>
>> New measurements are taken approximately 40 Hz or at the frequency of
>> the reference (whichever is lower).
>>
>> The driver currently uses the averaging factor N=2 which prioritizes
>> a fast response time to track dynamic changes in the phase. But for
>> applications requiring a very stable and precise reading of the average
>> phase offset, and where rapid changes are not expected, a higher factor
>> would be appropriate.
>>
>> Add devlink device parameter phase_offset_avg_factor to allow a user
>> set tune the averaging factor via devlink interface.
>>
>> Tested-by: Prathosh Satish <Prathosh.Satish@microchip.com>
>> Signed-off-by: Ivan Vecera <ivecera@redhat.com>
>> ---
>>   Documentation/networking/devlink/zl3073x.rst |  4 ++
>>   drivers/dpll/zl3073x/core.c                  |  6 +-
>>   drivers/dpll/zl3073x/core.h                  |  8 ++-
>>   drivers/dpll/zl3073x/devlink.c               | 67 ++++++++++++++++++++
>>   4 files changed, 82 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/networking/devlink/zl3073x.rst b/Documentation/networking/devlink/zl3073x.rst
>> index 4b6cfaf386433..ddd159e39e616 100644
>> --- a/Documentation/networking/devlink/zl3073x.rst
>> +++ b/Documentation/networking/devlink/zl3073x.rst
>> @@ -20,6 +20,10 @@ Parameters
>>        - driverinit
>>        - Set the clock ID that is used by the driver for registering DPLL devices
>>          and pins.
>> +   * - ``phase_offset_avg_factor``
>> +     - runtime
>> +     - Set the factor for the exponential moving average used by DPLL phase
>> +       measurement block. The value has to be in range <0, 15>.
> 
> Maybe put the text in the commit message here as well?

Do you mean to put the equation and details from commit message here?
This is pretty long.

Ivan


  reply	other threads:[~2025-09-10 16:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-10 10:32 [PATCH net-next] dpll: zl3073x: Allow to use custom phase measure averaging factor Ivan Vecera
2025-09-10 12:33 ` Przemek Kitszel
2025-09-10 12:34 ` Vadim Fedorenko
2025-09-10 13:30   ` Ivan Vecera
2025-09-10 16:13 ` Andrew Lunn
2025-09-10 16:50   ` Ivan Vecera [this message]
2025-09-10 17:06     ` Andrew Lunn
2025-09-10 17:31       ` 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=0817610a-e3dd-427e-b0ad-c2d503bb8a4f@redhat.com \
    --to=ivecera@redhat.com \
    --cc=Prathosh.Satish@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).