All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adrian Schmutzler" <mail@adrianschmutzler.de>
To: "'Marek Behun'" <marek.behun@nic.cz>
Cc: <linux-leds@vger.kernel.org>
Subject: RE: [PATCH v2 1/2] dt-bindings: leds: add LED_FUNCTION for wlan2g/wlan5g
Date: Sun, 20 Sep 2020 01:09:49 +0200	[thread overview]
Message-ID: <00da01d68ed9$f967dfb0$ec379f10$@adrianschmutzler.de> (raw)
In-Reply-To: <20200920002846.22a76e03@nic.cz>

[-- Attachment #1: Type: text/plain, Size: 891 bytes --]

> > As far as I understand it, the color/function system does not provide a
> comparable lever, as the final name is only constructed in led-core.c?
> >
> 
> The files in /sys/class/leds/ are symlinks. The actual files are in /sys/devices/
> somewhere. If you know the path of your LED in the device hierarchy, you
> can find it that way. If your script can access the LED by reading device-tree,
> you can implement your script so that you can find the LED in the hiearchy in
> /sys/devices/ (or simply byt reading where do the symlinks in
> /sys/class/leds/ point to).

Thanks for that pointer; unfortunately though, I was only able to retrieve lists of leds in [device:]color:function syntax and lists of the DT nodes, but nothing where a single node from DT is linked or can be related to just one of the [device:]color:function identifiers.

Best

Adrian

> 
> Marek

[-- Attachment #2: openpgp-digital-signature.asc --]
[-- Type: application/pgp-signature, Size: 834 bytes --]

  reply	other threads:[~2020-09-19 23:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-19 19:24 [PATCH v2 1/2] dt-bindings: leds: add LED_FUNCTION for wlan2g/wlan5g Adrian Schmutzler
2020-09-19 19:24 ` [PATCH v2 2/2] dt-bindings: leds: add LED_FUNCTION_RSSI Adrian Schmutzler
2020-09-19 20:31 ` [PATCH v2 1/2] dt-bindings: leds: add LED_FUNCTION for wlan2g/wlan5g Marek Behun
2020-09-19 21:40   ` Adrian Schmutzler
2020-09-19 22:28     ` Marek Behun
2020-09-19 23:09       ` Adrian Schmutzler [this message]
2020-09-20  0:06         ` Marek Behun
2020-09-20  9:59           ` Adrian Schmutzler
2020-09-20 13:16   ` Jacek Anaszewski
2020-09-20 13:37     ` Marek Behun
2020-09-20 14:59       ` Jacek Anaszewski
2020-09-20 15:28         ` Marek Behun
2020-09-20 17:44           ` Jacek Anaszewski
2020-09-21 22:10           ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2020-09-19 17:27 Adrian Schmutzler
2020-09-19 21:45 ` Adrian Schmutzler
2020-09-23 21:04   ` Rob Herring

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='00da01d68ed9$f967dfb0$ec379f10$@adrianschmutzler.de' \
    --to=mail@adrianschmutzler.de \
    --cc=linux-leds@vger.kernel.org \
    --cc=marek.behun@nic.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.