[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <518397C60809E147AF5323E0420B992E3EA5A510@DBDE01.ent.ti.com>
Date: Thu, 10 Jan 2013 04:11:42 +0000
From: "Philip, Avinash" <avinashphilip@...com>
To: Thierry Reding <thierry.reding@...onic-design.de>
CC: "tony@...mide.com" <tony@...mide.com>,
"paul@...an.com" <paul@...an.com>,
"linux@....linux.org.uk" <linux@....linux.org.uk>,
"Cousson, Benoit" <b-cousson@...com>,
"Hiremath, Vaibhav" <hvaibhav@...com>,
"AnilKumar, Chimata" <anilkumar@...com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"Nori, Sekhar" <nsekhar@...com>,
"Hebbar, Gururaja" <gururaja.hebbar@...com>,
"Bedia, Vaibhav" <vaibhav.bedia@...com>
Subject: RE: [PATCH 3/7] pwm: pwm-tiehrpwm: Update the clock handling of
pwm-tiehrpwm driver
On Wed, Jan 02, 2013 at 19:08:43, Thierry Reding wrote:
> On Wed, Jan 02, 2013 at 06:54:50PM +0530, Philip Avinash wrote:
> > The clock framework has changed and it's now better to invoke
> > clock_prepare_enable() and clk_disable_unprepare() rather than the
> > legacy clk_enable() and clk_disable() calls. This patch converts the
> > pwm-tiehrpwm driver to the new framework.
> >
> > Signed-off-by: Philip Avinash <avinashphilip@...com>
> > Cc: Thierry Reding <thierry.reding@...onic-design.de>
> > ---
> > In 3.8-rc1, common clock frame work support added to AM335x.
> >
> > drivers/pwm/pwm-tiehrpwm.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/pwm/pwm-tiehrpwm.c b/drivers/pwm/pwm-tiehrpwm.c
> > index 72a6dd4..af6f162 100644
> > --- a/drivers/pwm/pwm-tiehrpwm.c
> > +++ b/drivers/pwm/pwm-tiehrpwm.c
> > @@ -341,7 +341,7 @@ static int ehrpwm_pwm_enable(struct pwm_chip *chip, struct pwm_device *pwm)
> > configure_polarity(pc, pwm->hwpwm);
> >
> > /* Enable TBCLK before enabling PWM device */
> > - clk_enable(pc->tbclk);
> > + clk_prepare_enable(pc->tbclk);
>
> I apparently didn't catch this before, but maybe it would be useful to
> check the return value here to make sure we only proceed if the clock
> can actually be enabled.
Ok I will check return value & make it return status of pwm_enable().
I will send it as individual patch in next series. I am waiting for
reviews / acceptance of HWMOD and clock tree node patches.
Thanks
Avinash
>
> Thierry
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists