From: Ian Lartey <ian@slimlogic.co.uk>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, ldewangan@nvidia.com,
j-keerthy@ti.com, gg@slimlogic.co.uk, cooloney@gmail.com,
rpurdie@rpsys.net, grant.likely@secretlab.ca,
rob.herring@calxeda.com, sameo@linux.intel.com,
broonie@opensource.wolfsonmicro.com
Subject: Re: [PATCH v2 1/2] leds: Add support for Palmas LEDs
Date: Thu, 28 Feb 2013 23:35:50 +0000 [thread overview]
Message-ID: <512FE9D6.1010907@slimlogic.co.uk> (raw)
In-Reply-To: <512FA39D.2060005@wwwdotorg.org>
On 28/02/13 18:36, Stephen Warren wrote:
> On 02/28/2013 08:21 AM, Ian Lartey wrote:
>> The Palmas familly of chips has LED support. This is not always muxed
>> to output pins so depending on the setting of the mux this driver
>> will create the appropriate LED class devices.
>
>> +static struct of_device_id of_palmas_match_tbl[] = {
>> + { .compatible = "ti,palmas-leds", },
>> + { /* end */ }
>> +};
>
> Is there DT binding documentation for this compatible value somewhere?
I think with the other palmas DT discussions this may be subject
to change. Once thay are resolved we'll get the documentation updated
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2013-02-28 23:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 15:21 [PATCH v2 1/2] leds: Add support for Palmas LEDs Ian Lartey
2013-02-28 15:21 ` [PATCH v2 2/2] leds: Kconfig " Ian Lartey
2013-02-28 18:36 ` [PATCH v2 1/2] leds: Add support " Stephen Warren
2013-02-28 23:35 ` Ian Lartey [this message]
2013-03-12 18:57 ` Bryan Wu
2013-03-12 19:10 ` Mark Brown
2013-03-12 21:15 ` Bryan Wu
2013-03-12 23:32 ` Ian Lartey
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=512FE9D6.1010907@slimlogic.co.uk \
--to=ian@slimlogic.co.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cooloney@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=gg@slimlogic.co.uk \
--cc=grant.likely@secretlab.ca \
--cc=j-keerthy@ti.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=rpurdie@rpsys.net \
--cc=sameo@linux.intel.com \
--cc=swarren@wwwdotorg.org \
/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).