From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Raul Piper <raulpblooper@gmail.com>,
linux-leds@vger.kernel.org,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Possible Sysfs for led class drivers
Date: Thu, 11 Aug 2016 22:38:34 +0200 [thread overview]
Message-ID: <57ACE24A.6080609@gmail.com> (raw)
In-Reply-To: <CAEwN+MBZqpKT5U+K93SdDQe4mCno3qULHy6=OZfjGcnTuUuKpg@mail.gmail.com>
Hi Raul,
On 08/11/2016 03:27 PM, Raul Piper wrote:
> Hi,
> I have scanned through some of the led sysfs interfaces of my hardware
> boards inside the /sys/class/leds and found these
> brightness,
> max_brightness
> trigger
> uevent
> invert
> sata
>
> I want to know can we add our own custom sysfs interface ?
> Does there exists a default list of interfaces provided by the led
> class subsystem? like brightness, max_brightness,trigger,uevent ,etc??
You can add custom sysfs attributes by initializing "groups" property
of struct led_classdev.
--
Best regards,
Jacek Anaszewski
prev parent reply other threads:[~2016-08-11 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 13:27 Possible Sysfs for led class drivers Raul Piper
2016-08-11 20:38 ` Jacek Anaszewski [this message]
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=57ACE24A.6080609@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-leds@vger.kernel.org \
--cc=raulpblooper@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).