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:   Fri, 21 Oct 2022 05:50:26 -0700
From:   Richard Cochran <>
To:     Sarath Babu Naidu Gaddam <>
Subject: Re: [PATCH net-next V2] dt-bindings: net: ethernet-controller: Add

On Thu, Oct 20, 2022 at 11:41:10PM -0600, Sarath Babu Naidu Gaddam wrote:
> There is currently no standard property to pass PTP device index
> information to ethernet driver when they are independent.
> ptp-hardware-clock property will contain phandle to PTP clock node.
> Freescale driver currently has this implementation but it will be
> good to agree on a generic (optional) property name to link to PTP
> phandle to Ethernet node. In future or any current ethernet driver
> wants to use this method of reading the PHC index,they can simply use
> this generic name and point their own PTP clock node, instead of
> creating separate property names in each ethernet driver DT node.
> axiethernet driver uses this method when PTP support is integrated.
> Example:
> 	fman0: fman@...0000 {
> 		ptp-hardware-clock = <&ptp_timer0>;
> 	}
> 	ptp_timer0: ptp-timer@...e000 {
> 		compatible = "fsl,fman-ptp-timer";
> 		reg = <0x0 0x1afe000 0x0 0x1000>;
> 	}
> Signed-off-by: Sarath Babu Naidu Gaddam <>

Acked-by: Richard Cochran <>

Powered by blists - more mailing lists