From: Andrew Lunn <andrew@lunn.ch>
To: Ivan Vecera <ivecera@redhat.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
netdev@vger.kernel.org,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jiri Pirko <jiri@resnulli.us>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Michal Schmidt <mschmidt@redhat.com>,
Petr Oros <poros@redhat.com>
Subject: Re: [PATCH net-next 1/2] dt-bindings: dpll: Add clock ID property
Date: Mon, 4 Aug 2025 20:45:05 +0200 [thread overview]
Message-ID: <1419bca0-b85a-4d4b-af1a-b0540c25933a@lunn.ch> (raw)
In-Reply-To: <f96b3236-f8e6-40c1-afb2-7e76894462f9@redhat.com>
> Let's say we have a SyncE setup with two network controllers where each
> of them feeds a DPLL channel with recovered clock received from some of
> its PHY. The DPLL channel cleans/stabilizes this input signal (generates
> phase aligned signal locked to the same frequency as the input one) and
> routes it back to the network controller.
>
> +-----------+
> +--| NIC 1 |<-+
> | +-----------+ |
> | |
> | RxCLK TxCLK |
> | |
> | +-----------+ |
> +->| channel 1 |--+
> |-- DPLL ---|
> +->| channel 2 |--+
> | +-----------+ |
> | |
> | RxCLK TxCLK |
> | |
> | +-----------+ |
> +--| NIC 2 |<-+
> +-----------+
>
> The PHCs implemented by the NICs have associated the ClockIdentity
> (according IEEE 1588-2008) whose value is typically derived from
> the NIC's MAC address using EUI-64. The DPLL channel should be
> registered to DPLL subsystem using the same ClockIdentity as the PHC
> it drives. In above example DPLL channel 1 should have the same clock ID
> as NIC1 PHC and channel 2 as NIC2 PHC.
>
> During the discussion, Andrew had the idea to provide NIC phandles
> instead of clock ID values.
>
> Something like this:
>
> diff --git a/Documentation/devicetree/bindings/dpll/dpll-device.yaml
> b/Documenta
> tion/devicetree/bindings/dpll/dpll-device.yaml
> index fb8d7a9a3693f..159d9253bc8ae 100644
> --- a/Documentation/devicetree/bindings/dpll/dpll-device.yaml
> +++ b/Documentation/devicetree/bindings/dpll/dpll-device.yaml
> @@ -33,6 +33,13 @@ properties:
> items:
> enum: [pps, eec]
>
> + ethernet-handles:
> + description:
> + List of phandles to Ethernet devices, one per DPLL instance. Each of
> + these handles identifies Ethernet device that uses particular DPLL
> + instance to synchronize its hardware clock.
> + $ref: /schemas/types.yaml#/definitions/phandle-array
> +
I personally would not use a list. I would have a node per channel,
and within that node, have the ethernet-handle property. This gives
you a more flexible scheme where you can easily add more per channel
properties in the future.
It took us a while to understand what you actually wanted. The ASCII
art helps. So i would include that and some text in the binding.
Andrew
next prev parent reply other threads:[~2025-08-04 18:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 17:10 [PATCH net-next 0/2] dpll: zl3073x: Read clock ID from device property Ivan Vecera
2025-07-17 17:10 ` [PATCH net-next 1/2] dt-bindings: dpll: Add clock ID property Ivan Vecera
2025-07-18 6:55 ` Krzysztof Kozlowski
2025-07-18 12:16 ` Ivan Vecera
2025-07-21 9:23 ` Krzysztof Kozlowski
2025-07-21 12:54 ` Ivan Vecera
2025-07-23 6:25 ` Krzysztof Kozlowski
2025-07-23 7:23 ` Ivan Vecera
2025-08-03 11:12 ` Krzysztof Kozlowski
2025-08-04 18:26 ` Ivan Vecera
2025-08-04 18:45 ` Andrew Lunn [this message]
2025-08-05 15:26 ` Ivan Vecera
2025-08-05 15:31 ` Andrew Lunn
2025-07-17 17:11 ` [PATCH net-next 2/2] dpll: zl3073x: Initialize clock ID from device property 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=1419bca0-b85a-4d4b-af1a-b0540c25933a@lunn.ch \
--to=andrew@lunn.ch \
--cc=Prathosh.Satish@microchip.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=poros@redhat.com \
--cc=robh@kernel.org \
--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
all inboxes | Powered by JetHome®