On 5/15/2011 4:28 PM, Russell King - ARM Linux wrote:
On Sun, May 15, 2011 at 01:00:31AM -0700, Dmitry Torokhov wrote:
On Fri, May 13, 2011 at 06:13:21PM +0530, Mohan Pallaka wrote:
For chip drivers that support both pwm and non-pwm modes
would encounter compilation errors if the platform
On Fri, May 13, 2011 at 06:13:21PM +0530, Mohan Pallaka wrote:
For chip drivers that support both pwm and non-pwm modes
would encounter compilation errors if the platform doesn't
have support for pwm though the chip is programmed to work
in non-pwm mode. Add __weak attributed pwm functions to
On Fri, May 13, 2011 at 06:13:21PM +0530, Mohan Pallaka wrote:
For chip drivers that support both pwm and non-pwm modes
would encounter compilation errors if the platform doesn't
have support for pwm though the chip is programmed to work
in non-pwm mode. Add __weak attributed pwm functions to
On Sun, May 15, 2011 at 01:00:31AM -0700, Dmitry Torokhov wrote:
On Fri, May 13, 2011 at 06:13:21PM +0530, Mohan Pallaka wrote:
For chip drivers that support both pwm and non-pwm modes
would encounter compilation errors if the platform doesn't
have support for pwm though the chip is
For chip drivers that support both pwm and non-pwm modes
would encounter compilation errors if the platform doesn't
have support for pwm though the chip is programmed to work
in non-pwm mode. Add __weak attributed pwm functions to avoid
compilation issues in these scenarios.
Change-Id:
For chip drivers that support both pwm and non-pwm modes
would encounter compilation errors if the platform doesn't
have support for pwm though the chip is programmed to work
in non-pwm mode. Add __weak attributed pwm functions to avoid
compilation issues in these scenarios.
Change-Id:
