From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, donald.hunter@gmail.com,
vadim.fedorenko@linux.dev, arkadiusz.kubalewski@intel.com,
saeedm@nvidia.com, leon@kernel.org, tariqt@nvidia.com
Subject: Re: [PATCH net-next v3 1/2] dpll: add clock quality level attribute and op
Date: Mon, 28 Oct 2024 10:14:03 -0700 [thread overview]
Message-ID: <20241028101403.67577dd9@kernel.org> (raw)
In-Reply-To: <Zw93LS5X5PXXgb8-@nanopsycho.orion>
On Wed, 16 Oct 2024 10:19:57 +0200 Jiri Pirko wrote:
> >> Not sure what do you mean by "clock info". Dpll device and clock is kind
> >> of the same thing. The dpll device is identified by clock-id. I see no
> >> other attributes on the way this direction to more extend dpll attr
> >> namespace.
> >
> >I'm not an expert but I think the standard definition of a DPLL
> >does not include a built-in oscillator, if that's what you mean.
>
> Okay. Then the clock-id we have also does not make much sense.
> Anyway, what is your desire exactly? Do you want to have a nest attr
> clock-info to contain this quality-level attr? Or something else?
I thought clock-id is basically clockid_t, IOW a reference.
I wish that the information about timekeepers was exposed
by the time subsystem rather than DPLL. Something like clock_getres().
next prev parent reply other threads:[~2024-10-28 17:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 8:11 [PATCH net-next v3 0/2] dpll: expose clock quality level Jiri Pirko
2024-10-14 8:11 ` [PATCH net-next v3 1/2] dpll: add clock quality level attribute and op Jiri Pirko
2024-10-14 8:54 ` Kubalewski, Arkadiusz
2024-10-15 14:26 ` Jakub Kicinski
2024-10-15 14:38 ` Jiri Pirko
2024-10-15 15:01 ` Jakub Kicinski
2024-10-16 8:19 ` Jiri Pirko
2024-10-18 7:07 ` Jiri Pirko
2024-10-28 17:14 ` Jakub Kicinski [this message]
2024-10-29 12:52 ` Jiri Pirko
2024-10-29 13:51 ` Jakub Kicinski
2024-10-29 14:41 ` Jiri Pirko
2024-10-16 8:21 ` Jiri Pirko
2024-10-15 14:50 ` Vadim Fedorenko
2024-10-15 14:56 ` Jiri Pirko
2024-10-15 15:01 ` Vadim Fedorenko
2024-10-16 8:17 ` Jiri Pirko
2024-10-14 8:11 ` [PATCH net-next v3 2/2] net/mlx5: DPLL, Add clock quality level op implementation Jiri Pirko
2024-10-14 8:57 ` Kubalewski, Arkadiusz
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=20241028101403.67577dd9@kernel.org \
--to=kuba@kernel.org \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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;
as well as URLs for NNTP newsgroup(s).