Let me be more specific, consider an environment where there is an
APE and Power Management subsystem(separate IC but on same
board/platform)
APE has a pwm module and Power Management SubSystem also has pwm
module. Both are part of the platform.
Not there exists two drivers in a single
- Original Message -
From: Arun Murthy arun.mur...@stericsson.com
The existing pwm based led and backlight driver makes use of the
pwm(include/linux/pwm.h). So all the board specific pwm drivers will
be exposing the same set of function name as in include/linux/pwm.h.
As a result
On Tue, Sep 28, 2010 at 06:23:24PM +0530, Hemanth V wrote:
- Original Message - From: Arun Murthy
arun.mur...@stericsson.com
The existing pwm based led and backlight driver makes use of the
pwm(include/linux/pwm.h). So all the board specific pwm drivers will
be exposing the same
On Tue, Sep 28, 2010 at 08:06:11AM -0500, Samuel Ortiz wrote:
On Tue, Sep 28, 2010 at 06:23:24PM +0530, Hemanth V wrote:
- Original Message - From: Arun Murthy
arun.mur...@stericsson.com
The existing pwm based led and backlight driver makes use of the
pwm(include/linux/pwm.h). So all
Arun MURTHY wrote:
Shouldn't PWM_DEVICES select HAVE_PWM?
No not required, the entire concept is to remove HAVE_PWM and use
PWM_CORE.
Well in patch 4 you say that PWM_CORE is currently limited to ARM.
Furthermore you
change the pwm-backlight and pwm-led Kconfig entries to depend on
Arun MURTHY wrote:
Shouldn't PWM_DEVICES select HAVE_PWM?
No not required, the entire concept is to remove HAVE_PWM and use
PWM_CORE.
Well in patch 4 you say that PWM_CORE is currently limited to ARM.
Furthermore you
change the pwm-backlight and pwm-led Kconfig entries to depend
