From: Dmitry Torokhov <dmitry.torokhov@gmail.com> To: Vasily Khoruzhick <anarsoul@gmail.com> Cc: Ben Dooks <ben-linux@fluff.org>, Kukjin Kim <kgene.kim@samsung.com>, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-input@vger.kernel.org Subject: Re: [PATCH] Input: s3c2410_ts: Move to clk_prepare_enable/clk_disable_unprepare Date: Tue, 8 Jul 2014 18:00:49 -0700 [thread overview] Message-ID: <20140709010049.GC14935@core.coreip.homeip.net> (raw) In-Reply-To: <1404155377-2862-1-git-send-email-anarsoul@gmail.com> On Mon, Jun 30, 2014 at 10:09:37PM +0300, Vasily Khoruzhick wrote: > Use clk_prepare_enable/clk_disable_unprepare to make the driver > work properly with common clock framework. > > Signed-off-by: Vasily Khoruzhick <anarsoul@gmail.com> > --- > drivers/input/touchscreen/s3c2410_ts.c | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/drivers/input/touchscreen/s3c2410_ts.c b/drivers/input/touchscreen/s3c2410_ts.c > index 19cb247..c0e0baa 100644 > --- a/drivers/input/touchscreen/s3c2410_ts.c > +++ b/drivers/input/touchscreen/s3c2410_ts.c > @@ -264,7 +264,7 @@ static int s3c2410ts_probe(struct platform_device *pdev) > return -ENOENT; > } > > - clk_enable(ts.clock); > + clk_prepare_enable(ts.clock); > dev_dbg(dev, "got and enabled clocks\n"); > > ts.irq_tc = ret = platform_get_irq(pdev, 0); > @@ -369,7 +369,7 @@ static int s3c2410ts_remove(struct platform_device *pdev) > free_irq(ts.irq_tc, ts.input); > del_timer_sync(&touch_timer); > > - clk_disable(ts.clock); > + clk_disable_unprepare(ts.clock); > clk_put(ts.clock); > > input_unregister_device(ts.input); > @@ -383,7 +383,7 @@ static int s3c2410ts_suspend(struct device *dev) > { > writel(TSC_SLEEP, ts.io + S3C2410_ADCTSC); > disable_irq(ts.irq_tc); > - clk_disable(ts.clock); > + clk_disable_unprepare(ts.clock); Do we really need to unprepare on suspend? Why simply disabling is not enough here? Thanks. > > return 0; > } > @@ -393,7 +393,7 @@ static int s3c2410ts_resume(struct device *dev) > struct platform_device *pdev = to_platform_device(dev); > struct s3c2410_ts_mach_info *info = dev_get_platdata(&pdev->dev); > > - clk_enable(ts.clock); > + clk_prepare_enable(ts.clock); > enable_irq(ts.irq_tc); > > /* Initialise registers */ > -- > 2.0.0 > -- Dmitry
WARNING: multiple messages have this Message-ID (diff)
From: dmitry.torokhov@gmail.com (Dmitry Torokhov) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] Input: s3c2410_ts: Move to clk_prepare_enable/clk_disable_unprepare Date: Tue, 8 Jul 2014 18:00:49 -0700 [thread overview] Message-ID: <20140709010049.GC14935@core.coreip.homeip.net> (raw) In-Reply-To: <1404155377-2862-1-git-send-email-anarsoul@gmail.com> On Mon, Jun 30, 2014 at 10:09:37PM +0300, Vasily Khoruzhick wrote: > Use clk_prepare_enable/clk_disable_unprepare to make the driver > work properly with common clock framework. > > Signed-off-by: Vasily Khoruzhick <anarsoul@gmail.com> > --- > drivers/input/touchscreen/s3c2410_ts.c | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/drivers/input/touchscreen/s3c2410_ts.c b/drivers/input/touchscreen/s3c2410_ts.c > index 19cb247..c0e0baa 100644 > --- a/drivers/input/touchscreen/s3c2410_ts.c > +++ b/drivers/input/touchscreen/s3c2410_ts.c > @@ -264,7 +264,7 @@ static int s3c2410ts_probe(struct platform_device *pdev) > return -ENOENT; > } > > - clk_enable(ts.clock); > + clk_prepare_enable(ts.clock); > dev_dbg(dev, "got and enabled clocks\n"); > > ts.irq_tc = ret = platform_get_irq(pdev, 0); > @@ -369,7 +369,7 @@ static int s3c2410ts_remove(struct platform_device *pdev) > free_irq(ts.irq_tc, ts.input); > del_timer_sync(&touch_timer); > > - clk_disable(ts.clock); > + clk_disable_unprepare(ts.clock); > clk_put(ts.clock); > > input_unregister_device(ts.input); > @@ -383,7 +383,7 @@ static int s3c2410ts_suspend(struct device *dev) > { > writel(TSC_SLEEP, ts.io + S3C2410_ADCTSC); > disable_irq(ts.irq_tc); > - clk_disable(ts.clock); > + clk_disable_unprepare(ts.clock); Do we really need to unprepare on suspend? Why simply disabling is not enough here? Thanks. > > return 0; > } > @@ -393,7 +393,7 @@ static int s3c2410ts_resume(struct device *dev) > struct platform_device *pdev = to_platform_device(dev); > struct s3c2410_ts_mach_info *info = dev_get_platdata(&pdev->dev); > > - clk_enable(ts.clock); > + clk_prepare_enable(ts.clock); > enable_irq(ts.irq_tc); > > /* Initialise registers */ > -- > 2.0.0 > -- Dmitry
next prev parent reply other threads:[~2014-07-09 1:00 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-30 19:09 [PATCH] Input: s3c2410_ts: Move to clk_prepare_enable/clk_disable_unprepare Vasily Khoruzhick 2014-06-30 19:09 ` Vasily Khoruzhick 2014-07-08 11:50 ` Tomasz Figa 2014-07-08 11:50 ` Tomasz Figa 2014-07-09 1:00 ` Dmitry Torokhov [this message] 2014-07-09 1:00 ` Dmitry Torokhov 2014-07-09 9:13 ` Vasily Khoruzhick 2014-07-09 9:13 ` Vasily Khoruzhick 2014-07-23 6:09 ` Dmitry Torokhov 2014-07-23 6:09 ` Dmitry Torokhov 2014-07-23 7:59 ` Vasily Khoruzhick 2014-07-23 7:59 ` Vasily Khoruzhick
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=20140709010049.GC14935@core.coreip.homeip.net \ --to=dmitry.torokhov@gmail.com \ --cc=anarsoul@gmail.com \ --cc=ben-linux@fluff.org \ --cc=kgene.kim@samsung.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-input@vger.kernel.org \ --cc=linux-samsung-soc@vger.kernel.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.