Hello, I was not very descriptive with the patches, sorry about that.
I am working on a set of devices where I wish to expose custom system clocks. Because we will be using different technologies for different hardware setups, the goal is to develop custom clock drivers using the POSIX interface provided by the kernel. This provides the advantage that the components comprising the final product can be broken down into distinct pieces that could be interchanged based on the requirements of the system. Also, there are added advantages with having your own clock driver, e.g. custom IOCTLS. However, there is one issue for this setup to work correctly: fd clock support is limited. The kernel does provide the ability to implement your own POSIX clocks, but the daemons providing ptp clock support do not have the ability to synchronize any system based POSIX clock, just the standard, predefined clocks. Thus I created this patch series. The first patch just implements basic POSIX clock operations (open, close). The second patch integrates the clock operations into the existing phc clock operations and the final patch adds an additional -d parameter, where you can specify a clock device when running in software clock mode, e.g. -d /dev/custom_clock0. I am open to suggestions or any constructive criticism on the idea. Sorry if I am being a bit vague but I can't get into too much detail :) Regards, Dimitrios On Mon, Nov 5, 2018 at 4:06 PM Richard Cochran <[email protected]> wrote: > On Mon, Nov 05, 2018 at 12:00:40PM +0100, Dimitrios Katsaros wrote: > > This patch adds dedicated logic for opening and closing posix clocks. > > We will need this for adding logic to ptp4l for using clocks that > > may not be ptp clocks. > > Tell us about the use case, please. > > Thanks, > Richard >
_______________________________________________ Linuxptp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
