From: Kurt Kanzenbach <kurt@linutronix.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Richard Cochran <richardcochran@gmail.com>,
Kamil Alkhouri <kamil.alkhouri@hs-offenburg.de>,
ilias.apalodimas@linaro.org
Subject: Re: [RFC PATCH 7/9] net: dsa: hellcreek: Add PTP status LEDs
Date: Fri, 19 Jun 2020 10:45:36 +0200 [thread overview]
Message-ID: <87366rqw9b.fsf@kurt> (raw)
In-Reply-To: <20200618174650.GI240559@lunn.ch>
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
Hi Andrew,
On Thu Jun 18 2020, Andrew Lunn wrote:
> On Thu, Jun 18, 2020 at 08:40:27AM +0200, Kurt Kanzenbach wrote:
>> The switch has two controllable I/Os which are usually connected to LEDs. This
>> is useful to immediately visually see the PTP status.
>>
>> These provide two signals:
>>
>> * is_gm
>>
>> This LED can be activated if the current device is the grand master in that
>> PTP domain.
>>
>> * sync_good
>>
>> This LED can be activated if the current device is in sync with the network
>> time.
>>
>> Expose these via the LED framework to be controlled via user space
>> e.g. linuxptp.
>
> Hi Kurt
>
> Is the hardware driving these signals at all? Or are these just
> suggested names in the documentation? It would not be an issue to have
> user space to configure them to use the heartbeat trigger, etc?
These are more like GPIOs. If a 1 is set into the register then the
hardware drives the signal to high. The names are from the
documentation:
* sync_good: This signal indicates that the switch is in sync
* is_gm: This signal indicates that the switch is the grand master
However, these signals have to be set by user space. Most likely these
signals are connected to LEDs.
Thanks,
Kurt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-06-19 8:45 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 6:40 [RFC PATCH 0/9] Hirschmann Hellcreek DSA driver Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 1/9] net: dsa: Add tag handling for Hirschmann Hellcreek switches Kurt Kanzenbach
2020-06-18 13:42 ` Andrew Lunn
2020-06-18 6:40 ` [RFC PATCH 2/9] net: dsa: Add DSA driver " Kurt Kanzenbach
2020-06-18 15:22 ` Andrew Lunn
2020-06-19 8:12 ` Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 3/9] net: dsa: hellcreek: Add PTP clock support Kurt Kanzenbach
2020-06-18 15:46 ` Jakub Kicinski
2020-06-19 8:13 ` Kurt Kanzenbach
2020-06-18 17:23 ` Andrew Lunn
2020-06-19 8:26 ` Kurt Kanzenbach
2020-06-19 13:40 ` Andrew Lunn
2020-06-22 11:52 ` Kurt Kanzenbach
2020-06-24 13:03 ` Richard Cochran
2020-06-25 7:08 ` Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 4/9] net: dsa: hellcreek: Add support for hardware timestamping Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 5/9] net: dsa: hellcreek: Add TAPRIO offloading support Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 6/9] net: dsa: hellcreek: Add debugging mechanisms Kurt Kanzenbach
2020-06-18 17:34 ` Andrew Lunn
2020-06-19 8:36 ` Kurt Kanzenbach
2020-06-19 13:42 ` Andrew Lunn
2020-06-22 12:32 ` Kurt Kanzenbach
2020-06-22 13:55 ` Andrew Lunn
2020-06-23 6:07 ` Kurt Kanzenbach
2020-06-22 14:14 ` Vladimir Oltean
2020-06-23 6:04 ` Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 7/9] net: dsa: hellcreek: Add PTP status LEDs Kurt Kanzenbach
2020-06-18 17:46 ` Andrew Lunn
2020-06-19 8:45 ` Kurt Kanzenbach [this message]
2020-06-19 13:52 ` Andrew Lunn
2020-06-18 6:40 ` [RFC PATCH 8/9] dt-bindings: Add vendor prefix for Hirschmann Kurt Kanzenbach
2020-06-18 6:40 ` [RFC PATCH 9/9] dt-bindings: net: dsa: Add documentation for Hellcreek switches Kurt Kanzenbach
2020-06-18 13:47 ` Andrew Lunn
2020-06-19 8:47 ` Kurt Kanzenbach
2020-06-19 13:56 ` Andrew Lunn
2020-06-22 12:02 ` Kurt Kanzenbach
2020-06-22 13:49 ` Andrew Lunn
2020-06-23 6:09 ` Kurt Kanzenbach
2020-06-18 17:40 ` Florian Fainelli
2020-06-19 8:48 ` Kurt Kanzenbach
2020-06-22 12:05 ` Kurt Kanzenbach
2020-06-26 17:11 ` Florian Fainelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87366rqw9b.fsf@kurt \
--to=kurt@linutronix.de \
--cc=andrew@lunn.ch \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=kamil.alkhouri@hs-offenburg.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=vivien.didelot@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).