From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id CFD6FD1A631 for ; Fri, 9 Jan 2026 14:12:22 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 77D6860791; Fri, 9 Jan 2026 14:12:22 +0000 (UTC) X-Virus-Scanned: amavis at osuosl.org Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavis, port 10024) with ESMTP id TaGpMKtNVeIQ; Fri, 9 Jan 2026 14:12:21 +0000 (UTC) X-Comment: SPF check N/A for local connections - client-ip=140.211.166.142; helo=lists1.osuosl.org; envelope-from=intel-wired-lan-bounces@osuosl.org; receiver= DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 005306073C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=osuosl.org; s=default; t=1767967941; bh=xcr1hWAXxXMTm+MOI2pLQIo/wtCHSaw2hi1H8FmkX8c=; h=Date:From:To:Cc:References:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=liseZA4xihWJUgAmzZqd4Wz9gd629XQ0m+ohaAhw4SQly3l3xDIOqkrbP2V9nCpMZ grLLDyxqkTejHY8icygVAwsdtTMMmeCacb1/SwGKBzXlAuvIFp4sD/u9p/y2KTdmW7 s8Bd1STrrYgtg5cIev6xURkHuKa4gEkJOaH/jm2yEcp6xTxXKAllnLrNLxtF5cy6v+ uIrzlkpPvZNavmfEI3IfknptrcbHaxPQktqJeOBgHyeIJx75n/MELka9I6ZZB2jmva 807f8ifRGe56ZUqJr7Z3EVlr1xT2pHgKjXp41g9Ij+Xdtrmvx3mOgDG2XCo3TLe8Kc mF40BgO4FYrOw== Received: from lists1.osuosl.org (lists1.osuosl.org [140.211.166.142]) by smtp3.osuosl.org (Postfix) with ESMTP id 005306073C; Fri, 9 Jan 2026 14:12:20 +0000 (UTC) Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists1.osuosl.org (Postfix) with ESMTP id E475512E for ; Fri, 9 Jan 2026 14:12:19 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id D5FEF80BC7 for ; Fri, 9 Jan 2026 14:12:19 +0000 (UTC) X-Virus-Scanned: amavis at osuosl.org Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavis, port 10024) with ESMTP id WL_zoT5YKAdi for ; Fri, 9 Jan 2026 14:12:19 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=170.10.129.124; helo=us-smtp-delivery-124.mimecast.com; envelope-from=ivecera@redhat.com; receiver= DMARC-Filter: OpenDMARC Filter v1.4.2 smtp1.osuosl.org D195A8095E DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org D195A8095E Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by smtp1.osuosl.org (Postfix) with ESMTPS id D195A8095E for ; Fri, 9 Jan 2026 14:12:18 +0000 (UTC) Received: from mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-609-wRIAoh3BOniKE_S44Jwm1g-1; Fri, 09 Jan 2026 09:12:11 -0500 X-MC-Unique: wRIAoh3BOniKE_S44Jwm1g-1 X-Mimecast-MFC-AGG-ID: wRIAoh3BOniKE_S44Jwm1g_1767967928 Received: from mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id D95E31956058; Fri, 9 Jan 2026 14:12:07 +0000 (UTC) Received: from [10.44.33.222] (unknown [10.44.33.222]) by mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 11B1030002D2; Fri, 9 Jan 2026 14:12:00 +0000 (UTC) Message-ID: Date: Fri, 9 Jan 2026 15:11:59 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Ivan Vecera To: Krzysztof Kozlowski Cc: Eric Dumazet , Tony Nguyen , Rob Herring , Leon Romanovsky , Andrew Lunn , linux-rdma@vger.kernel.org, Przemek Kitszel , Arkadiusz Kubalewski , intel-wired-lan@lists.osuosl.org, Jakub Kicinski , Paolo Abeni , devicetree@vger.kernel.org, Conor Dooley , Jiri Pirko , Richard Cochran , Prathosh Satish , Vadim Fedorenko , netdev@vger.kernel.org, Mark Bloch , linux-kernel@vger.kernel.org, Tariq Toukan , Alexander Lobakin , Jonathan Lemon , Krzysztof Kozlowski , Saeed Mahameed , "David S. Miller" References: <20260108182318.20935-1-ivecera@redhat.com> <20260108182318.20935-2-ivecera@redhat.com> <20260109-wonderful-acoustic-civet-e030da@quoll> Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.4 X-Mailman-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1767967937; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=xcr1hWAXxXMTm+MOI2pLQIo/wtCHSaw2hi1H8FmkX8c=; b=KmjZ2ynYShcgjzjjfmGZ9KuezdGqqRwks3w+LXz61Ogi6lQPukOc21rSMLP2IKWq8mWaXB bnuJqoeM7NudSEWqhfxagbnK+Ben13c96nACdf6vfwyTJHr1oIxEil1mvN9OGiH0oeLJVg SAbCUCWwKJEncxkamujGygiHSzdirAE= X-Mailman-Original-Authentication-Results: smtp1.osuosl.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com X-Mailman-Original-Authentication-Results: smtp1.osuosl.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=KmjZ2ynY Subject: Re: [Intel-wired-lan] [PATCH net-next 01/12] dt-bindings: dpll: add common dpll-pin-consumer schema X-BeenThere: intel-wired-lan@osuosl.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Intel Wired Ethernet Linux Kernel Driver Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-wired-lan-bounces@osuosl.org Sender: "Intel-wired-lan" On 1/9/26 11:22 AM, Ivan Vecera wrote: > > > On 1/9/26 10:48 AM, Krzysztof Kozlowski wrote: >> On Thu, Jan 08, 2026 at 07:23:07PM +0100, Ivan Vecera wrote: >>> Introduce a common schema for DPLL pin consumers. Devices such as >>> Ethernet >>> controllers and PHYs may require connections to DPLL pins for >>> Synchronous >>> Ethernet (SyncE) or other frequency synchronization tasks. >>> >>> Defining these properties in a shared schema ensures consistency across >>> different device types that consume DPLL resources. >>> >>> Signed-off-by: Ivan Vecera >>> --- >>>   .../bindings/dpll/dpll-pin-consumer.yaml      | 30 +++++++++++++++++++ >>>   MAINTAINERS                                   |  1 + >>>   2 files changed, 31 insertions(+) >>>   create mode 100644 Documentation/devicetree/bindings/dpll/dpll-pin- >>> consumer.yaml >>> >>> diff --git a/Documentation/devicetree/bindings/dpll/dpll-pin- >>> consumer.yaml b/Documentation/devicetree/bindings/dpll/dpll-pin- >>> consumer.yaml >>> new file mode 100644 >>> index 0000000000000..60c184c18318a >>> --- /dev/null >>> +++ b/Documentation/devicetree/bindings/dpll/dpll-pin-consumer.yaml >>> @@ -0,0 +1,30 @@ >>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) >>> +%YAML 1.2 >>> +--- >>> +$id: http://devicetree.org/schemas/dpll/dpll-pin-consumer.yaml# >>> +$schema: http://devicetree.org/meta-schemas/core.yaml# >>> + >>> +title: DPLL Pin Consumer >>> + >>> +maintainers: >>> +  - Ivan Vecera >>> + >> >> You miss select. Without it this binding is no-op. > > Will fix. > >>> +description: | >> >> Drop | > > Will do. > >>> +  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 2) dtschema does not contain dpll-device and dpll-pin schemas now, I 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 Thanks, Ivan > Will do. > > Thanks for advice... > > Ivan >