The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ivan Vecera <ivecera@redhat.com>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>, netdev@vger.kernel.org
Cc: 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 15:30:06 +0200	[thread overview]
Message-ID: <b9be10d5-16de-4ad5-80eb-df28c5b5ae29@redhat.com> (raw)
In-Reply-To: <5ca46c45-96c3-4ad8-b00a-2494ae12d88b@linux.dev>



On 10. 09. 25 2:34 odp., Vadim Fedorenko wrote:
> On 10.09.2025 11:32, 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>
> 
> [...]
> 
>> +static int
>> +zl3073x_devlink_param_phase_avg_factor_set(struct devlink *devlink, 
>> u32 id,
>> +                       struct devlink_param_gset_ctx *ctx,
>> +                       struct netlink_ext_ack *extack)
>> +{
>> +    struct zl3073x_dev *zldev = devlink_priv(devlink);
>> +    u8 avg_factor, dpll_meas_ctrl;
>> +    int rc;
>> +
>> +    /* Read DPLL phase measurement control register */
>> +    rc = zl3073x_read_u8(zldev, ZL_REG_DPLL_MEAS_CTRL, &dpll_meas_ctrl);
>> +    if (rc)
>> +        return rc;
>> +
>> +    /* Convert requested factor to register value */
>> +    if (ctx->val.vu8 < 15)
>> +        avg_factor = ctx->val.vu8 + 1;
>> +    else
>> +        avg_factor = 0;
>> +
> 
> This looks like avg_factor = (ctx->val.vu8 + 1) & 0x0f;
> The same logic can be applied for get() function assuming we are aware of
> unsigned roll-over...

Yes, I know about this trick but I wanted to use more readable code and
leave potential optimization to the compiler.

Ivan


  reply	other threads:[~2025-09-10 13:30 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 [this message]
2025-09-10 16:13 ` Andrew Lunn
2025-09-10 16:50   ` Ivan Vecera
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=b9be10d5-16de-4ad5-80eb-df28c5b5ae29@redhat.com \
    --to=ivecera@redhat.com \
    --cc=Prathosh.Satish@microchip.com \
    --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 \
    --cc=vadim.fedorenko@linux.dev \
    /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