netdev - Re: [PATCH v1 1/2] dt-binding: ptp: add bindings document for dte based ptp clock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 14 Jun 2017 11:18:54 -0700
From:   Ray Jui <ray.jui@...adcom.com>
To:     Arun Parameswaran <arun.parameswaran@...adcom.com>,
        Richard Cochran <richardcochran@...il.com>
Cc:     Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        netdev@...r.kernel.org, bcm-kernel-feedback-list@...adcom.com
Subject: Re: [PATCH v1 1/2] dt-binding: ptp: add bindings document for dte
 based ptp clock



On 6/13/17 10:46 AM, Arun Parameswaran wrote:
> 
> Hi Richard,
> 
> On 17-06-12 10:09 PM, Richard Cochran wrote:
>> On Mon, Jun 12, 2017 at 01:26:00PM -0700, Arun Parameswaran wrote:
>>> +Example:
>>> +
>>> +ptp_dte: ptp_dte@...af650 {
>>> +	compatible = "brcm,ptp-dte";
>>> +	reg = <0x180af650 0x10>;
>>> +	status = "okay";
>>> +};
>> This patch set looks okay, as far as it goes, but how does one
>> actually use the clock?
>>
>> How does one connect this node to an Ethernet MAC, for example?
> In some of the SoC's, the DTE's NCO is synced in hardware with the Ethernet's
> 1588 Shim NCO (used for time-stamping the packets). We are working on getting
> all the future SoC's synced this way (for Ethernet).
> 

So apparently you do not need any phandle based DT binding defined for
the connection between the Ethernet device node and the PTP device node?

> In other scenarios, we use an user-space app to perform the sync based on
> time-stamps from external hardware sources like the Wi-Fi.
>> Thanks,
>> Richard
>