On Fri, Jul 01, 2016 at 07:50:18PM +0300, Ivan Oleynikov wrote:
> Working with PHC through a symlink instead of directly passing /dev/ptp0 to
> `ptl4l -p` can be useful when you have multiple PTP clocks in your system and
> the order in which they are registered is unpredictable (as well as name of
> your
> desired PHC file in /dev/).
Right, they are unpredictable. Because we have the ethtool info,
ptp4l doesn't care and neither should you.
> So you have to look at
> /sys/class/ptp/ptp*/{clock_name, device} to find the name of your device.
No, don't do that...
> Alternative solution would be to create udev rule matching ptp device with
> specific DRIVERS, KERNELS, etc. that will add a symlink (e.g. /dev/my_ptp in
> the
> first example) to your device.
and don't do that either.
Just let your MAC driver advertise the associated PHC index, and leave
udev, etc, alone.
Thanks,
Richard
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Linuxptp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
