[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7934306e-08f9-478a-a218-1b03dbfa8a3b@linux.dev>
Date: Tue, 15 Oct 2024 16:01:12 +0100
From: Vadim Fedorenko <vadim.fedorenko@...ux.dev>
To: Jiri Pirko <jiri@...nulli.us>
Cc: Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
donald.hunter@...il.com, arkadiusz.kubalewski@...el.com, saeedm@...dia.com,
leon@...nel.org, tariqt@...dia.com
Subject: Re: [PATCH net-next v3 1/2] dpll: add clock quality level attribute
and op
On 15/10/2024 15:56, Jiri Pirko wrote:
> Tue, Oct 15, 2024 at 04:50:41PM CEST, vadim.fedorenko@...ux.dev wrote:
>> On 15/10/2024 15:26, Jakub Kicinski wrote:
>>> On Mon, 14 Oct 2024 10:11:32 +0200 Jiri Pirko wrote:
>>>> + type: enum
>>>> + name: clock-quality-level
>>>> + doc: |
>>>> + level of quality of a clock device. This mainly applies when
>>>> + the dpll lock-status is not DPLL_LOCK_STATUS_LOCKED.
>>>> + The current list is defined according to the table 11-7 contained
>>>> + in ITU-T G.8264/Y.1364 document. One may extend this list freely
>>>> + by other ITU-T defined clock qualities, or different ones defined
>>>> + by another standardization body (for those, please use
>>>> + different prefix).
>>>
>>> uAPI extensibility aside - doesn't this belong to clock info?
>>> I'm slightly worried we're stuffing this attr into DPLL because
>>> we have netlink for DPLL but no good way to extend clock info.
>>
>> There is a work going on by Maciek Machnikowski about extending clock
>> info. But the progress is kinda slow..
>
> Do you have some info about this? A list of attrs at least would help.
The mailing list conversation started in this thread:
https://lore.kernel.org/netdev/20240813125602.155827-1-maciek@machnikowski.net/
But the idea was presented back at the latest Netdevconf:
https://netdevconf.org/0x18/sessions/tutorial/introduction-to-ptp-on-linux-apis.html
>>
>>>> + entries:
>>>> + -
>>>> + name: itu-opt1-prc
>>>> + value: 1
>>>> + -
>>>> + name: itu-opt1-ssu-a
>>>> + -
>>>> + name: itu-opt1-ssu-b
>>>> + -
>>>> + name: itu-opt1-eec1
>>>> + -
>>>> + name: itu-opt1-prtc
>>>> + -
>>>> + name: itu-opt1-eprtc
>>>> + -
>>>> + name: itu-opt1-eeec
>>>> + -
>>>> + name: itu-opt1-eprc
>>>> + render-max: true
>>>
>>> Why render max? Just to align with other unnecessary max defines in
>>> the file?
>>
Powered by blists - more mailing lists