From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1E3CA3806B3 for ; Mon, 12 Jan 2026 18:07:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.133.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768241242; cv=none; b=C8M342fnCuEah+nq3d4OXCZqnPak5fX1iQ17UWid0Uibi4hgyy77k+pXwp3yB/vELb2EUhaxvJEGyui3gaJuhZ5giagPo0Vnd+A+L2dHnE5ah1/j95hfBoYMOtmUY32xOOhCoTqit4k+8pYHWJepvH9w9L/9dQ9ucSrbnqqfJro= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768241242; c=relaxed/simple; bh=NvDyeDgHvqmkUu7ojmnVMY3szfEihgKDFkrLZZfycdY=; h=Message-ID:Date:MIME-Version:Subject:From:To:Cc:References: In-Reply-To:Content-Type; b=kBbSmsCH70fCs5c9SGk0fFsxZyuNaGq4crWVd7Dwv1fC18SaH5U/tMO3IUVlAPB/5wPNCd0xt/wAdr8UxgJ8GItSYA1hzlWAuCy+enBUa58QobnnCJCeyJEUhrah6UFUBmHlp8aKCX/CITFpyPPtOm+GEz0XNSmWXy65KcfXz44= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=Gq9jUM0S; arc=none smtp.client-ip=170.10.133.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="Gq9jUM0S" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1768241240; 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=id5XPqkuM+zrpYOCKhCCCDsyMuntmPe6ENzF1N8Jw8o=; b=Gq9jUM0SRHAjsmXLoDXlDMgwXA967SaVXfXhhPomhhGpHuaF+8k2sQx8OreBV/ZpbTw1Ct 6u9ODAh2LBgfT+6wZyPRrn/lH3zz7/w+Sgfky/Etto3sqRzV7pH0YXYAZvnfYW192T8/ym Qk5TLkuI8JPLqHY6fkLCoRU/tsymLu4= Received: from mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-14-GFrrsXd3Pdau7aSSVBCihg-1; Mon, 12 Jan 2026 13:07:13 -0500 X-MC-Unique: GFrrsXd3Pdau7aSSVBCihg-1 X-Mimecast-MFC-AGG-ID: GFrrsXd3Pdau7aSSVBCihg_1768241230 Received: from mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.17]) (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-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id EF7ED18002C4; Mon, 12 Jan 2026 18:07:09 +0000 (UTC) Received: from [10.44.34.128] (unknown [10.44.34.128]) by mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id DE4E019560AB; Mon, 12 Jan 2026 18:07:02 +0000 (UTC) Message-ID: <1fc327e0-fd35-4192-80c8-7b73bb9cb9c3@redhat.com> Date: Mon, 12 Jan 2026 19:07:01 +0100 Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [Intel-wired-lan] [PATCH net-next 01/12] dt-bindings: dpll: add common dpll-pin-consumer schema 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.0 on 10.30.177.17 On 1/12/26 5:48 PM, Ivan Vecera wrote: > > > On 1/12/26 5:14 PM, Krzysztof Kozlowski wrote: >> 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. > > OK, will remove this patch from the series and create PR against > dtschema and ... > >>> 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. > > ... include dpll.yaml and dpll-pin.yaml as well. Well, after dtschema investigation, I should make a PR with dpll-pin-consumer.yaml and dpll-pin-producer.yaml. Correct? Thanks, Ivan