diff options
| author | Vladimir Oltean <olteanv@gmail.com> | 2019-12-27 03:08:07 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2019-12-30 20:14:27 -0800 |
| commit | 3a323ed7c9c6d60af05bada0efe7a8ef56cf317f (patch) | |
| tree | b9e76a9b11942b1fb6709bd5ab705f45246948ff | |
| parent | d00bdc0a8839de9a5c9be5af2a79dbf8e0087689 (diff) | |
Documentation: net: dsa: sja1105: Remove text about taprio base-time limitation
Since commit 86db36a347b4 ("net: dsa: sja1105: Implement state machine
for TAS with PTP clock source"), this paragraph is no longer true. So
remove it.
Signed-off-by: Vladimir Oltean <olteanv@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
| -rw-r--r-- | Documentation/networking/dsa/sja1105.rst | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/Documentation/networking/dsa/sja1105.rst b/Documentation/networking/dsa/sja1105.rst index eef20d0bcf7c..64553d8d91cb 100644 --- a/Documentation/networking/dsa/sja1105.rst +++ b/Documentation/networking/dsa/sja1105.rst @@ -230,12 +230,6 @@ simultaneously on two ports. The driver checks the consistency of the schedules against this restriction and errors out when appropriate. Schedule analysis is needed to avoid this, which is outside the scope of the document. -At the moment, the time-aware scheduler can only be triggered based on a -standalone clock and not based on PTP time. This means the base-time argument -from tc-taprio is ignored and the schedule starts right away. It also means it -is more difficult to phase-align the scheduler with the other devices in the -network. - Device Tree bindings and board design ===================================== |