From: Stephen Warren <swarren@wwwdotorg.org>
To: Roland Stigge <stigge@antcom.de>
Cc: riku.voipio@iki.fi, bryan.wu@canonical.com, rpurdie@rpsys.net,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, aletes.xgr@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] leds: Add DT support for leds-pca9532
Date: Sat, 16 Jun 2012 09:06:36 -0600 [thread overview]
Message-ID: <4FDCA0FC.5000409@wwwdotorg.org> (raw)
In-Reply-To: <1339855851-9171-1-git-send-email-stigge@antcom.de>
On 06/16/2012 08:10 AM, Roland Stigge wrote:
> This patch adds DT support for leds-pca9532.
> +++ linux-2.6/Documentation/devicetree/bindings/leds/leds-pca9532.txt
> +- nxp,typecodes: groups of 2 bits for each of the 16 pins:
> + 0: None
> + 1: LED
> + 2: Beep
> + 3: GPIO
> +- nxp,statecodes: groups of 2 bits for each of the 16 pins:
> + 0: off
> + 1: on
> + 2: pwm0
> + 3: pwm1
> +
> +Optional properties:
> +- nxp,psc: array of 2 numbers: PSC values for the two PWM channels (see datasheet)
> +- nxp,pwm: array of 2 numbers: PWM values for the two PWM channels (see datasheet)
Shouldn't that all be exposed using a combination of the pinctrl
bindings that are in 3.5, and the PWM bindings that should be coming in 3.6?
next prev parent reply other threads:[~2012-06-16 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 14:10 [PATCH] leds: Add DT support for leds-pca9532 Roland Stigge
2012-06-16 15:06 ` Stephen Warren [this message]
2012-06-17 11:51 ` Roland Stigge
2012-06-17 18:02 ` Stephen Warren
2012-06-19 6:16 ` Thierry Reding
-- strict thread matches above, loose matches on Subject: below --
2014-09-09 13:28 Roland Stigge
[not found] ` <1410269280-8761-1-git-send-email-stigge-uj/7R2tJ6VmzQB+pC5nmwQ@public.gmane.org>
2014-09-09 18:08 ` Arnd Bergmann
2014-09-10 15:22 ` Roland Stigge
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=4FDCA0FC.5000409@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=aletes.xgr@gmail.com \
--cc=bryan.wu@canonical.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=riku.voipio@iki.fi \
--cc=rpurdie@rpsys.net \
--cc=stigge@antcom.de \
/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).