All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Tony Makkiel <tony.makkiel@daqri.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:36:49 +0200	[thread overview]
Message-ID: <575AD081.7040200@samsung.com> (raw)
In-Reply-To: <575AB8E3.4000401@daqri.com>

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.

-- 
Best regards,
Jacek Anaszewski

  reply	other threads:[~2016-06-10 14:36 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 [this message]
2016-06-10 15:22             ` Tony Makkiel
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=575AD081.7040200@samsung.com \
    --to=j.anaszewski@samsung.com \
    --cc=lenb@kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rpurdie@rpsys.net \
    --cc=tony.makkiel@daqri.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.