Transfer clock cleanup handling to the core device management code.

Signed-off-by: Geert Uytterhoeven <geert+rene...@glider.be>
---
 drivers/tty/serial/sh-sci.c | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/drivers/tty/serial/sh-sci.c b/drivers/tty/serial/sh-sci.c
index cba51da604253db6..9442961a198378c7 100644
--- a/drivers/tty/serial/sh-sci.c
+++ b/drivers/tty/serial/sh-sci.c
@@ -2216,7 +2216,7 @@ static struct uart_ops sci_uart_ops = {
 static int sci_init_clocks(struct sci_port *sci_port, struct device *dev)
 {
        /* Get the SCI functional clock. It's called "fck" on ARM. */
-       sci_port->fclk = clk_get(dev, "fck");
+       sci_port->fclk = devm_clk_get(dev, "fck");
        if (PTR_ERR(sci_port->fclk) == -EPROBE_DEFER)
                return -EPROBE_DEFER;
        if (!IS_ERR(sci_port->fclk))
@@ -2226,7 +2226,7 @@ static int sci_init_clocks(struct sci_port *sci_port, 
struct device *dev)
         * But it used to be called "sci_ick", and we need to maintain DT
         * backward compatibility.
         */
-       sci_port->fclk = clk_get(dev, "sci_ick");
+       sci_port->fclk = devm_clk_get(dev, "sci_ick");
        if (PTR_ERR(sci_port->fclk) == -EPROBE_DEFER)
                return -EPROBE_DEFER;
        if (!IS_ERR(sci_port->fclk))
@@ -2236,7 +2236,7 @@ static int sci_init_clocks(struct sci_port *sci_port, 
struct device *dev)
         * Not all SH platforms declare a clock lookup entry for SCI devices,
         * in which case we need to get the global "peripheral_clk" clock.
         */
-       sci_port->fclk = clk_get(dev, "peripheral_clk");
+       sci_port->fclk = devm_clk_get(dev, "peripheral_clk");
        if (!IS_ERR(sci_port->fclk))
                return 0;
 
@@ -2395,8 +2395,6 @@ static int sci_init_single(struct platform_device *dev,
 
 static void sci_cleanup_single(struct sci_port *port)
 {
-       clk_put(port->fclk);
-
        pm_runtime_disable(port->port.dev);
 }
 
-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to