From: Jiri Pirko <jiri@resnulli•us>
To: Ivan Vecera <ivecera@redhat•com>
Cc: netdev@vger•kernel.org, Andrew Lunn <andrew+netdev@lunn•ch>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel•com>,
"David S. Miller" <davem@davemloft•net>,
Donald Hunter <donald.hunter@gmail•com>,
Eric Dumazet <edumazet@google•com>,
Jakub Kicinski <kuba@kernel•org>,
Jonathan Corbet <corbet@lwn•net>,
Leon Romanovsky <leon@kernel•org>,
Mark Bloch <mbloch@nvidia•com>,
Michal Schmidt <mschmidt@redhat•com>,
Paolo Abeni <pabeni@redhat•com>,
Pasi Vaananen <pvaanane@redhat•com>,
Petr Oros <poros@redhat•com>,
Prathosh Satish <Prathosh.Satish@microchip•com>,
Saeed Mahameed <saeedm@nvidia•com>,
Shuah Khan <skhan@linuxfoundation•org>,
Simon Horman <horms@kernel•org>,
Tariq Toukan <tariqt@nvidia•com>,
Vadim Fedorenko <vadim.fedorenko@linux•dev>,
linux-doc@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-rdma@vger•kernel.org
Subject: Re: [PATCH net-next v3 1/2] dpll: add fractional frequency offset to pin-parent-device
Date: Tue, 5 May 2026 13:31:41 +0200 [thread overview]
Message-ID: <afnVGPD5sjpSXz--@FV6GYCPJ69> (raw)
In-Reply-To: <20260504155340.411063-2-ivecera@redhat.com>
Mon, May 04, 2026 at 05:53:39PM +0200, ivecera@redhat•com wrote:
>Add both fractional-frequency-offset (PPM) and
>fractional-frequency-offset-ppt (PPT) attributes to the
>pin-parent-device nested attribute set, alongside the existing
>top-level pin attributes. Both carry the same measurement at
>different precisions.
>
>Distinguish the two contexts in the ffo_get callback by passing
>dpll=NULL for the top-level call and a valid dpll pointer for the
>nested per-parent call. This allows drivers to report a different
>value per parent DPLL if needed. Update mlx5 and zl3073x drivers
>to return -ENODATA for the context they do not yet support.
>
>Add documentation for both FFO attributes to dpll.rst.
>
>Signed-off-by: Ivan Vecera <ivecera@redhat•com>
Reviewed-by: Jiri Pirko <jiri@nvidia•com>
next prev parent reply other threads:[~2026-05-05 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 15:53 [PATCH net-next v3 0/2] dpll: rework fractional frequency offset reporting Ivan Vecera
2026-05-04 15:53 ` [PATCH net-next v3 1/2] dpll: add fractional frequency offset to pin-parent-device Ivan Vecera
2026-05-05 11:31 ` Jiri Pirko [this message]
2026-05-07 1:33 ` Jakub Kicinski
2026-05-07 6:12 ` Ivan Vecera
2026-05-07 14:47 ` Jakub Kicinski
2026-05-07 11:08 ` Jiri Pirko
2026-05-04 15:53 ` [PATCH net-next v3 2/2] dpll: zl3073x: report FFO as DPLL vs input reference offset Ivan Vecera
2026-05-05 14:34 ` Petr Oros
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=afnVGPD5sjpSXz--@FV6GYCPJ69 \
--to=jiri@resnulli$(echo .)us \
--cc=Prathosh.Satish@microchip$(echo .)com \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=arkadiusz.kubalewski@intel$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=donald.hunter@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=ivecera@redhat$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=leon@kernel$(echo .)org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=mbloch@nvidia$(echo .)com \
--cc=mschmidt@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=poros@redhat$(echo .)com \
--cc=pvaanane@redhat$(echo .)com \
--cc=saeedm@nvidia$(echo .)com \
--cc=skhan@linuxfoundation$(echo .)org \
--cc=tariqt@nvidia$(echo .)com \
--cc=vadim.fedorenko@linux$(echo .)dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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