The latency from software responding to the timer and then firing an event
on a gpio would be eliminated.
No, the latency increases when using PHC. That is the whole point.
In the scenario I am describing, a hardware event is fired immediately
when the PHC timer expires in hardware. That
Right, and getting back to original question, if you want multiple
periodic outputs at the same time, you simply provide multiple
channels in the driver and then assign each pin its own channel.
That is the solution I am currently using. However, it involves a
custom driver to assign a
On Fri, Mar 23, 2018 at 05:00:18PM +, Keller, Jacob E wrote:
> > The PTP subsystem only allows one pin to be mapped to one channel for
> > periodic
> > outputs. Why does the ptp subsystem force only allowing one pin index to
> > one a
> > periodic output channel? It seems like a common use
> -Original Message-
> From: Alex Fontaine [mailto:fonta...@arlut.utexas.edu]
> Sent: Friday, March 23, 2018 9:26 AM
> To: linuxptp-devel@lists.sourceforge.net
> Subject: [Linuxptp-devel] PTP Periodic Output to Multiple Pins
>
> The PTP subsystem only allows one pin to be mapped to one
On Fri, Mar 23, 2018 at 11:26:29AM -0500, Alex Fontaine wrote:
> The PTP subsystem only allows one pin to be mapped to one channel for
> periodic outputs. Why does the ptp subsystem force only allowing one pin
> index to one a periodic output channel?
Because this has been sufficient up until
On Fri, Mar 23, 2018 at 11:03:50AM -0500, Alex Fontaine wrote:
> The kernel documentation states the ability to use POSIX timers with the PTP
> hardware clocks. This does not appear to be implemented in the ptp
> subsystem drivers. What is preventing this timer interface from being
>
The PTP subsystem only allows one pin to be mapped to one channel for
periodic outputs. Why does the ptp subsystem force only allowing one pin
index to one a periodic output channel? It seems like a common use case to
want to assign a single periodic output to multiple pins.
The current
The kernel documentation states the ability to use POSIX timers with the PTP
hardware clocks. This does not appear to be implemented in the ptp
subsystem drivers. What is preventing this timer interface from being
implemented?
Previous discussions[1] indicate the PHC timer functionality
The first version of this path series had formatting issues. Therefore, I send
the patches once more, with (hopefully) correct formatting.
This patch series changes phc2sys. It implements the possibility to use a
configuration file, enables the usage of long options and allows configuring
the
Signed-off-by: Peter Schneider
---
phc2sys.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/phc2sys.c b/phc2sys.c
index 5c54055..c2f0d8e 100644
--- a/phc2sys.c
+++ b/phc2sys.c
@@ -1286,6 +1286,7 @@ static void usage(char *progname)
Signed-off-by: Peter Schneider
---
phc2sys.c | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/phc2sys.c b/phc2sys.c
index c2f0d8e..278ab56 100644
--- a/phc2sys.c
+++ b/phc2sys.c
@@ -1317,11 +1317,13 @@ int main(int argc, char *argv[])
char
Signed-off-by: Peter Schneider
---
phc2sys.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/phc2sys.c b/phc2sys.c
index 278ab56..c6ab788 100644
--- a/phc2sys.c
+++ b/phc2sys.c
@@ -877,7 +877,8 @@ static int init_pmc(struct config *cfg, struct node *node,
Signed-off-by: Peter Schneider
---
phc2sys.8 | 103 --
1 file changed, 101 insertions(+), 2 deletions(-)
diff --git a/phc2sys.8 b/phc2sys.8
index 4fc4fa3..fa2dbc9 100644
--- a/phc2sys.8
+++ b/phc2sys.8
@@ -8,10 +8,16 @@
13 matches
Mail list logo