From: dbaryshkov@gmail.com (Dmitry Eremin-Solenikov)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] implement a generic PWM framework - once again
Date: Tue, 28 Jun 2011 12:23:58 +0000 (UTC) [thread overview]
Message-ID: <iuch4t$6ba$1@dough.gmane.org> (raw)
In-Reply-To: 1309255368-9775-1-git-send-email-s.hauer@pengutronix.de
Hi,
Sascha Hauer wrote:
> Hi All,
>
> The following implements a generic pwm framework and adds a user
> for it. I already posted this series back in January. Based on
> the comments I received I added some details about the motivation
> for adding such a framework and not using the led or hwmon framework
> to patch 1/2.
> I also added some documentation to Documentation/pwm.txt.
>
> This patch does not change the user API for PWMs, in particular
> it does not enforce any sleep/nonsleep context to the PWM users.
> The patch merely puts the status quo into a core wrapper to be able
> to register multiple PWM drivers in the system. Improvements to
> the API can still be made later once we have at least a place
> in the kernel to collect the existing PWM drivers.
Just a small question: on PXA (just for example) PWMs are registered
from arch/arm via arch_initcall. Will your subsystem work for such early
registration (of course after moving PXA driver to drivers/pwm)?
--
With best wishes
Dmitry
prev parent reply other threads:[~2011-06-28 12:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 10:02 [RFC] implement a generic PWM framework - once again Sascha Hauer
2011-06-28 10:02 ` [PATCH 1/2] PWM: add pwm framework support Sascha Hauer
2011-06-28 12:27 ` Arnd Bergmann
2011-06-28 16:18 ` Sascha Hauer
2011-06-28 17:03 ` Arnd Bergmann
2011-06-29 8:50 ` Sascha Hauer
2011-06-29 11:00 ` Arnd Bergmann
2011-06-28 19:40 ` Matthias Kaehlcke
2011-06-28 10:02 ` [PATCH 2/2] pwm: Add a i.MX23/28 pwm driver Sascha Hauer
2011-06-28 10:28 ` Lothar Waßmann
2011-06-28 15:22 ` Arnd Bergmann
2011-06-28 12:23 ` Dmitry Eremin-Solenikov [this message]
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='iuch4t$6ba$1@dough.gmane.org' \
--to=dbaryshkov@gmail.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).