From: peter.ujfalusi@ti.com (Peter Ujfalusi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: omap3-overo: Add support for pwm-leds
Date: Fri, 25 Jan 2013 09:29:08 +0100 [thread overview]
Message-ID: <51024254.40208@ti.com> (raw)
In-Reply-To: <5101A43D.7080108@epfl.ch>
On 01/24/2013 10:14 PM, Florian Vaussard wrote:
> You are right. But then the pwm core must provide a way to know if the pwm
> access function are callable
> from atomic context or not (the gpio framework provides gpio_cansleep()).
> This implies a good amount of changes to the pwm framework, and currently we
> are the only driver using non-atomic access.
We have two drivers at the moment: pwm-twl and pwm-twl-led. However new out of
SoC PWM drivers might come (for example for palmas). So it worth take a look
at some generic implementation.
--
P?ter
next prev parent reply other threads:[~2013-01-25 8:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 17:56 [PATCH 0/2] ARM: dts: omap3-overo: Add pwm-leds and audio support Florian Vaussard
2013-01-23 17:56 ` [PATCH 1/2] ARM: dts: omap3-overo: Add support for pwm-leds Florian Vaussard
2013-01-24 15:19 ` Peter Ujfalusi
2013-01-24 15:42 ` Florian Vaussard
2013-01-24 15:45 ` Peter Ujfalusi
2013-01-24 16:50 ` Florian Vaussard
2013-01-24 17:08 ` Peter Ujfalusi
2013-01-24 21:14 ` Florian Vaussard
2013-01-25 8:29 ` Peter Ujfalusi [this message]
2013-01-25 12:07 ` Peter Ujfalusi
2013-01-25 12:21 ` Florian Vaussard
2013-01-25 12:30 ` Peter Ujfalusi
2013-01-23 17:56 ` [PATCH 2/2] ARM: dts: omap3-overo: Add audio support Florian Vaussard
2013-01-24 15:21 ` Peter Ujfalusi
2013-01-24 12:21 ` [PATCH 0/2] ARM: dts: omap3-overo: Add pwm-leds and " Benoit Cousson
2013-02-04 9:14 ` Florian Vaussard
2013-02-06 13:30 ` Benoit Cousson
2013-02-06 14:26 ` Philippe Rétornaz
2013-02-07 7:58 ` Peter Ujfalusi
2013-02-26 16:07 ` Florian Vaussard
2013-02-26 16:19 ` Benoit Cousson
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=51024254.40208@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).