linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Makkiel <tony.makkiel@daqri.com>
To: Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: linux-leds@vger.kernel.org, rpurdie@rpsys.net, rjw@rjwysocki.net,
	lenb@kernel.org
Subject: Re: [PATCH v3 1/1] leds: LED driver for TI LP3952 6-Channel Color LED
Date: Fri, 10 Jun 2016 16:22:28 +0100	[thread overview]
Message-ID: <575ADB34.4090604@daqri.com> (raw)
In-Reply-To: <575AD081.7040200@samsung.com>



On 10/06/16 15:36, Jacek Anaszewski wrote:
> On 06/10/2016 02:56 PM, Tony Makkiel wrote:
>>
>>
>>
>>>>>>> +
>>>>>>> +#ifdef CONFIG_ACPI
>>>>>>> +static const struct acpi_device_id lp3952_acpi_match[] = {
>>>>>>> +    {LP3952_NAME, 0},
>>>>>>> +    {}
>>>>>>> +};
>>>>>>
>>>>>> Could you please share how did you apply ACPI overlay?
>>>>>
>>>>> I am using the initrd ACPI method of Octavian's patch.
>>>>>
>>>>> https://lkml.org/lkml/2016/3/31/333
>>>>
>>>> Thanks. Would it be possible to define entries per each LED
>>>> connected to the LED controller, similarly as it is in case
>>>> of Device Tree bindings?:
>>>>
>>>> Documentation/devicetree/bindings/leds/common.txt
>>>>
>>>
>>> I am not sure. I did a quick skim through ACPI Spec 5.0.
>>> But couldn't find anything.
>>
>> Found it!, although not relevant for this driver. Please
>> see last page of
>> http://www.uefi.org/sites/default/files/resources/_DSD-device-properties-UUID.pdf
> 
> Great. The "Package" entries seem to use names compatible with the
> Device Tree properties documented in
> Documentation/devicetree/bindings/leds/common.txt.
> 
> Probably you could also provide LED name in the "Name" entry and obtain
> them in the driver directly from ACPI, similarly as it is accomplished
> in case of Device Tree.
> 
> led_name array from lp3952_register_led_classdev() could be removed
> then.

I don't think it is possible yet, maybe once there is an updated iasl compiler.
The current version does not even recognize _DSD.
> 

  reply	other threads:[~2016-06-10 15:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 10:46 [PATCH v3 1/1] leds: LED driver for TI LP3952 6-Channel Color LED Tony Makkiel
2016-06-09 12:11 ` Jacek Anaszewski
2016-06-09 15:20   ` Tony Makkiel
2016-06-10  8:26     ` Jacek Anaszewski
2016-06-10 11:39       ` Tony Makkiel
2016-06-10 12:56         ` Tony Makkiel
2016-06-10 14:36           ` Jacek Anaszewski
2016-06-10 15:22             ` Tony Makkiel [this message]
2016-06-10 14:36         ` Jacek Anaszewski
2016-06-10 15:18           ` Tony Makkiel

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=575ADB34.4090604@daqri.com \
    --to=tony.makkiel@daqri.com \
    --cc=j.anaszewski@samsung.com \
    --cc=lenb@kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rpurdie@rpsys.net \
    /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).