public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ivan Vecera <ivecera@redhat.com>
Cc: Eric Dumazet <edumazet@google.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Rob Herring <robh@kernel.org>, Leon Romanovsky <leon@kernel.org>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	linux-rdma@vger.kernel.org,
	Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
	intel-wired-lan@lists.osuosl.org,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
	Jiri Pirko <jiri@resnulli.us>,
	Richard Cochran <richardcochran@gmail.com>,
	Prathosh Satish <Prathosh.Satish@microchip.com>,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	netdev@vger.kernel.org, Mark Bloch <mbloch@nvidia.com>,
	linux-kernel@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>,
	Alexander Lobakin <aleksander.lobakin@intel.com>,
	Jonathan Lemon <jonathan.lemon@gmail.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Saeed Mahameed <saeedm@nvidia.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [PATCH net-next 01/12] dt-bindings: dpll: add common dpll-pin-consumer schema
Date: Mon, 12 Jan 2026 17:14:54 +0100	[thread overview]
Message-ID: <cbf482be-4aa8-488f-9f78-181f8f145c28@kernel.org> (raw)
In-Reply-To: <fd07e1f8-455c-464f-9760-9d16d450a7d5@redhat.com>

On 09/01/2026 15:11, Ivan Vecera wrote:
>>>> +  Common properties for devices that require connection to DPLL 
>>>> (Digital Phase
>>>> +  Locked Loop) pins for frequency synchronization (e.g. SyncE).
>>>> +
>>>> +properties:
>>>> +  dpll-pins:
>>>> +    $ref: /schemas/types.yaml#/definitions/phandle-array
>>>> +    description:
>>>> +      List of phandles to the DPLL pin nodes connected to this device.
>>>> +
>>>> +  dpll-pin-names:
>>>> +    $ref: /schemas/types.yaml#/definitions/string-array
>>>> +    description:
>>>> +      Names for the DPLL pins defined in 'dpll-pins', in the same 
>>>> order.
>>>> +
>>>> +dependencies:
>>>> +  dpll-pin-names: [ dpll-pins ]
>>>
>>> Binding should go to dtschema. See also commit
>>> 3282a891060aace02e3eed4789739768060cea32 in dtschema or other examples
>>> how to add new provider/consumer properties.
> 
> Quick questions... if the dpll pin consumer properties schema should go
> to dtschema...
> 
> 1) Should I remove this patch from this series? So this schema won't be
>     a part of kernel

Yes.

> 2) dtschema does not contain dpll-device and dpll-pin schemas now, I

The provider, so the #foo-cells should be in dtschema as well.

>     expect they should be added as well... or? I'm asking because there
>     is also e.g. hwlock-consumer.yaml in dtschema but no hwlock

hwlock-cells are missing, probably due to licensing.

Best regards,
Krzysztof

  reply	other threads:[~2026-01-12 16:15 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08 18:23 [PATCH net-next 00/12] dpll: Core improvements and ice E825-C SyncE support Ivan Vecera
2026-01-08 18:23 ` [PATCH net-next 01/12] dt-bindings: dpll: add common dpll-pin-consumer schema Ivan Vecera
2026-01-09  9:48   ` Krzysztof Kozlowski
2026-01-09 10:22     ` [Intel-wired-lan] " Ivan Vecera
2026-01-09 14:11       ` Ivan Vecera
2026-01-12 16:14         ` Krzysztof Kozlowski [this message]
2026-01-12 16:48           ` Ivan Vecera
2026-01-12 18:07             ` Ivan Vecera
2026-01-15 12:01   ` Ivan Vecera
2026-01-16 15:23     ` Rob Herring
2026-01-16 19:00       ` Ivan Vecera
2026-01-16 23:39         ` Rob Herring
2026-01-17 18:21           ` Ivan Vecera
2026-01-08 18:23 ` [PATCH net-next 02/12] dpll: Allow associating dpll pin with a firmware node Ivan Vecera
2026-01-09 15:46   ` Vadim Fedorenko
2026-01-08 18:23 ` [PATCH net-next 03/12] dpll: Add helpers to find DPLL pin fwnode Ivan Vecera
2026-01-09  9:55   ` Krzysztof Kozlowski
2026-01-09 10:22     ` Ivan Vecera
2026-01-12 16:16       ` Krzysztof Kozlowski
2026-01-12 16:52         ` Ivan Vecera
2026-01-09 14:19     ` Ivan Vecera
2026-01-12 16:20       ` Krzysztof Kozlowski
2026-01-12 16:55         ` Ivan Vecera
2026-01-08 18:23 ` [PATCH net-next 04/12] dpll: zl3073x: Associate pin with fwnode handle Ivan Vecera
2026-01-08 18:23 ` [PATCH net-next 05/12] dpll: Add notifier chain for dpll events Ivan Vecera
2026-01-09 16:12   ` Vadim Fedorenko
2026-01-08 18:23 ` [PATCH net-next 06/12] dpll: Support dynamic pin index allocation Ivan Vecera
2026-01-09 23:34   ` [Intel-wired-lan] " kernel test robot
2026-01-12 15:13   ` kernel test robot
2026-01-12 16:56     ` Ivan Vecera
2026-01-12 19:19   ` kernel test robot
2026-01-08 18:23 ` [PATCH net-next 07/12] dpll: zl3073x: Add support for mux pin type Ivan Vecera
2026-01-08 18:23 ` [PATCH net-next 08/12] dpll: Enhance and consolidate reference counting logic Ivan Vecera
2026-01-08 18:23 ` [PATCH net-next 09/12] dpll: Prevent duplicate registrations Ivan Vecera
2026-01-08 18:23 ` [PATCH net-next 10/12] dpll: Add reference count tracking support Ivan Vecera
2026-01-12 16:06   ` [Intel-wired-lan] " kernel test robot
2026-01-08 18:23 ` [PATCH net-next 11/12] drivers: Add support for DPLL reference count tracking Ivan Vecera
2026-01-08 18:23 ` [PATCH net-next 12/12] ice: dpll: Support E825-C SyncE and dynamic pin discovery Ivan Vecera
2026-01-09  6:15   ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-01-09 14:47     ` 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=cbf482be-4aa8-488f-9f78-181f8f145c28@kernel.org \
    --to=krzk@kernel.org \
    --cc=Prathosh.Satish@microchip.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=ivecera@redhat.com \
    --cc=jiri@resnulli.us \
    --cc=jonathan.lemon@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=richardcochran@gmail.com \
    --cc=robh@kernel.org \
    --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