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 X-Spam-Level: X-Spam-Status: No, score=-8.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6D2F7C2D0CD for ; Wed, 18 Dec 2019 20:02:27 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 419BD227BF for ; Wed, 18 Dec 2019 20:02:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576699347; bh=T5o/6QXjHZ/ae3B19+XCkNB3WMKQk1FH15KLecKeBVg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=rQI/4VXIGpAKFvTBdvzvQRIUV3ZUqnxHGqz2EmofpyaiOVZNJQqqBfhTFiunmBmws i/qqjEdYzbEwT7FDavbmBVVPxoSI0huqweKQqUxkCLv9k4up0dZQDSOPHWxYXFz3fK YkSJh2KxWVS677xXO6RxTDf79ar3W561ir0SiWyA= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727533AbfLRUC0 (ORCPT ); Wed, 18 Dec 2019 15:02:26 -0500 Received: from mail-ot1-f68.google.com ([209.85.210.68]:39741 "EHLO mail-ot1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726699AbfLRUC0 (ORCPT ); Wed, 18 Dec 2019 15:02:26 -0500 Received: by mail-ot1-f68.google.com with SMTP id 77so3922828oty.6; Wed, 18 Dec 2019 12:02:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=lCmnk+e3mjZ7dqkfu+pk+SY2OjT2ufDgkeX0yklAEgY=; b=fKNE5iCH89h/KTriz6roYWScqFeWMP0oX3mw2DNxxZfORqgcYEq9cFI95/IVinrjhr PzCOnkryVh+gUIGS8BmdXBQdutHDTE9ByjrLPQmsD9ixD3fCC5Ia0p9pE34C/yq73I5q 08O7e1qW5zhlRtYZh1f2YflijttlgePODcf4zSk4FYgR15UdOM5qZoS8BM7TqwPziDu3 n/iFSt6DCggs5JYBxLJQmxLm84ab4xCfGebjW779rswqhL3dmWWwA2ADXRpBVGnzH0U/ ZiCuBTzyMgBih/4T7JYhjnBaNNqqMqgMaa/X0t+EQNWCZ55xDSC7hMql7JbXTu1c6src uEzA== X-Gm-Message-State: APjAAAWooJ8GSf97MN4BJNGfwDEnqo3Xe/t6Rm4OS0tayFHBzFlY8dgX uNjKRysFLDmXkXQehnw5BQ== X-Google-Smtp-Source: APXvYqwkdmgyGQQMbO0R0qH+BwjO615U9NfrV287ftDD+CGe2pRxQUxR4bmfaRPQCxW6Ci/A/1c58g== X-Received: by 2002:a9d:3d0a:: with SMTP id a10mr789175otc.327.1576699345228; Wed, 18 Dec 2019 12:02:25 -0800 (PST) Received: from localhost (24-155-109-49.dyn.grandenetworks.net. [24.155.109.49]) by smtp.gmail.com with ESMTPSA id l7sm1145231oie.36.2019.12.18.12.02.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 18 Dec 2019 12:02:24 -0800 (PST) Date: Wed, 18 Dec 2019 14:02:24 -0600 From: Rob Herring To: Richard Cochran Cc: netdev@vger.kernel.org, David Miller , devicetree@vger.kernel.org, Andrew Lunn , Florian Fainelli , Heiner Kallweit , Jacob Keller , Mark Rutland , Miroslav Lichvar , Murali Karicheri , Willem de Bruijn , Wingman Kwok Subject: Re: [PATCH V6 net-next 08/11] dt-bindings: ptp: Introduce MII time stamping devices. Message-ID: <20191218200224.GA25825@bogus> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Mon, Dec 16, 2019 at 08:13:23AM -0800, Richard Cochran wrote: > This patch add a new binding that allows non-PHY MII time stamping > devices to find their buses. The new documentation covers both the > generic binding and one upcoming user. > > Signed-off-by: Richard Cochran > Reviewed-by: Andrew Lunn > --- > .../devicetree/bindings/ptp/ptp-ines.txt | 35 ++++++++++++++++ > .../devicetree/bindings/ptp/timestamper.txt | 41 +++++++++++++++++++ > 2 files changed, 76 insertions(+) > create mode 100644 Documentation/devicetree/bindings/ptp/ptp-ines.txt > create mode 100644 Documentation/devicetree/bindings/ptp/timestamper.txt > > diff --git a/Documentation/devicetree/bindings/ptp/ptp-ines.txt b/Documentation/devicetree/bindings/ptp/ptp-ines.txt > new file mode 100644 > index 000000000000..4c242bd1ce9c > --- /dev/null > +++ b/Documentation/devicetree/bindings/ptp/ptp-ines.txt > @@ -0,0 +1,35 @@ > +ZHAW InES PTP time stamping IP core > + > +The IP core needs two different kinds of nodes. The control node > +lives somewhere in the memory map and specifies the address of the > +control registers. There can be up to three port handles placed as > +attributes of PHY nodes. These associate a particular MII bus with a > +port index within the IP core. > + > +Required properties of the control node: > + > +- compatible: "ines,ptp-ctrl" > +- reg: physical address and size of the register bank > + > +Required format of the port handle within the PHY node: > + > +- timestamper: provides control node reference and > + the port channel within the IP core > + > +Example: > + > + tstamper: timestamper@60000000 { > + compatible = "ines,ptp-ctrl"; > + reg = <0x60000000 0x80>; > + }; > + > + ethernet@80000000 { > + ... > + mdio { > + ... > + ethernet-phy@3 { > + ... > + timestamper = <&tstamper 0>; > + }; > + }; > + }; > diff --git a/Documentation/devicetree/bindings/ptp/timestamper.txt b/Documentation/devicetree/bindings/ptp/timestamper.txt > new file mode 100644 > index 000000000000..70d636350582 > --- /dev/null > +++ b/Documentation/devicetree/bindings/ptp/timestamper.txt > @@ -0,0 +1,41 @@ > +Time stamps from MII bus snooping devices > + > +This binding supports non-PHY devices that snoop the MII bus and > +provide time stamps. In contrast to PHY time stamping drivers (which > +can simply attach their interface directly to the PHY instance), stand > +alone MII time stamping drivers use this binding to specify the > +connection between the snooping device and a given network interface. > + > +Non-PHY MII time stamping drivers typically talk to the control > +interface over another bus like I2C, SPI, UART, or via a memory mapped > +peripheral. This controller device is associated with one or more > +time stamping channels, each of which snoops on a MII bus. > + > +The "timestamper" property lives in a phy node and links a time > +stamping channel from the controller device to that phy's MII bus. > + > +Example: > + > + tstamper: timestamper@10000000 { unit-address needs a reg property. > + compatible = "ines,ts-ctrl"; Should be ines,ptp-ctrl? > + }; > + > + ethernet@20000000 { > + mdio { > + ethernet-phy@1 { > + timestamper = <&tstamper 0>; > + }; > + }; > + }; > + > + ethernet@30000000 { > + mdio { > + ethernet-phy@2 { > + timestamper = <&tstamper 1>; > + }; > + }; > + }; > + > +In this example, time stamps from the MII bus attached to phy@1 will > +appear on time stamp channel 0 (zero), and those from phy@2 appear on > +channel 1. > -- > 2.20.1 >