linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 2/5] i2c: pxa: prepare/unprepare clocks
Date: Mon, 17 Nov 2014 15:51:07 +0000	[thread overview]
Message-ID: <20141117155107.GU4042@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1416236863-20898-2-git-send-email-dbaryshkov@gmail.com>

On Mon, Nov 17, 2014 at 06:07:40PM +0300, Dmitry Eremin-Solenikov wrote:
> Change clk_enable/disable() calls to clk_prepare_enable() and
> clk_disable_unprepare().
> 
> Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
> ---
>  drivers/i2c/busses/i2c-pxa.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/i2c/busses/i2c-pxa.c b/drivers/i2c/busses/i2c-pxa.c
> index be671f7..2e75375 100644
> --- a/drivers/i2c/busses/i2c-pxa.c
> +++ b/drivers/i2c/busses/i2c-pxa.c
> @@ -1297,7 +1297,7 @@ static int i2c_pxa_suspend_noirq(struct device *dev)
>  	struct platform_device *pdev = to_platform_device(dev);
>  	struct pxa_i2c *i2c = platform_get_drvdata(pdev);
>  
> -	clk_disable(i2c->clk);
> +	clk_disable_unprepare(i2c->clk);

Since clk_unprepare() and clk_prepare() can sleep, it is unwise to call
these with IRQs disabled - the _noirq variants of these are run with
IRQs disabled.

-- 
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2014-11-17 15:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17 15:07 [PATCH V2 1/5] serial: pxa: prepare/unprepare clocks Dmitry Eremin-Solenikov
2014-11-17 15:07 ` [PATCH V2 2/5] i2c: " Dmitry Eremin-Solenikov
2014-11-17 15:51   ` Russell King - ARM Linux [this message]
2014-11-17 18:26   ` Wolfram Sang
2014-11-17 15:07 ` [PATCH V2 3/5] usb: gadget: pxa25x_udc: prepare/unprepare clocks in pxa-ssp Dmitry Eremin-Solenikov
2014-11-17 18:44   ` Robert Jarzmik
2014-11-17 20:05     ` Dmitry Eremin-Solenikov
2014-11-17 20:07       ` Russell King - ARM Linux
2014-11-17 20:09       ` Robert Jarzmik
2014-11-17 23:50       ` Dmitry Eremin-Solenikov
2014-11-19 20:29         ` Robert Jarzmik
2014-11-19 21:11           ` Dmitry Eremin-Solenikov
2014-11-22 13:56           ` Robert Jarzmik
2014-11-22 15:44             ` Dmitry Eremin-Solenikov
2014-11-22 17:18               ` Robert Jarzmik
2014-11-22 17:48                 ` Dmitry Eremin-Solenikov
2014-11-22 17:49                   ` Robert Jarzmik
2014-11-22 17:51                     ` Dmitry Eremin-Solenikov
2014-11-24  7:53                       ` Robert Jarzmik
2014-11-26 22:12                         ` Robert Jarzmik
2014-11-26 22:19                           ` Dmitry Eremin-Solenikov
     [not found]                             ` <87zjbd1tb0.fsf_-_@free.fr>
2014-11-26 22:39                               ` Lubbock interrupts fix (was lubbock udc phy) Dmitry Eremin-Solenikov
2014-11-18 15:49       ` [PATCH V2 3/5] usb: gadget: pxa25x_udc: prepare/unprepare clocks in pxa-ssp Felipe Balbi
2014-11-17 15:07 ` [PATCH V2 4/5] mfd: t7l66xb: prepare/unprepare clocks Dmitry Eremin-Solenikov
2014-11-18 13:14   ` Lee Jones
2014-11-17 15:07 ` [PATCH V2 5/5] mfd: tc6387xb: " Dmitry Eremin-Solenikov
2014-11-18 12:04   ` Lee Jones
2014-11-17 15:51 ` [PATCH V2 1/5] serial: pxa: " Russell King - ARM Linux

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=20141117155107.GU4042@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).