From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Matt Ranostay <mranostay@gmail.com>,
zonque@gmail.com, linux-input@vger.kernel.org,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 2/2] cap11xx: add LED support
Date: Tue, 23 Jun 2015 09:00:31 +0200 [thread overview]
Message-ID: <5589040F.5050605@samsung.com> (raw)
In-Reply-To: <20150622180828.GB15851@dtor-ws>
On 06/22/2015 08:08 PM, Dmitry Torokhov wrote:
[...]
>> +
>> + for_each_child_of_node(node, child) {
>> + led->cdev.name =
>> + of_get_property(child, "label", NULL) ? : child->name;
>> + led->cdev.default_trigger =
>> + of_get_property(child, "linux,default-trigger", NULL);
>
> Hmm, we do not have standard LEDs fwnode parser? Maybe we should have
> one.
We don't have one. That's something to be added.
--
Best Regards,
Jacek Anaszewski
prev parent reply other threads:[~2015-06-23 7:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 3:58 [PATCH v5 0/2] cap11xx: add LED support Matt Ranostay
2015-06-18 3:58 ` [PATCH v5 1/2] dt: add cap11xx LED documentation Matt Ranostay
2015-06-18 6:49 ` Jacek Anaszewski
2015-06-22 17:59 ` Dmitry Torokhov
2015-06-23 8:36 ` Jacek Anaszewski
[not found] ` <55891A84.1070509-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-06-23 17:23 ` Matt Ranostay
2015-06-23 18:07 ` Dmitry Torokhov
2015-06-23 18:24 ` Matt Ranostay
[not found] ` <CAKzfze_n7hf629=aUb6j-tcPcBLcwTH-a8yLJWS0cLM=dOkEVQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-23 18:52 ` Dmitry Torokhov
2015-06-24 7:28 ` Jacek Anaszewski
2015-06-24 7:44 ` Jacek Anaszewski
2015-06-18 3:58 ` [PATCH v5 2/2] cap11xx: add LED support Matt Ranostay
2015-06-18 6:51 ` Jacek Anaszewski
2015-06-20 2:32 ` Matt Ranostay
2015-06-22 18:08 ` Dmitry Torokhov
2015-06-23 7:00 ` 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=5589040F.5050605@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mranostay@gmail.com \
--cc=zonque@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 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.