[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56458323.6040506@ti.com>
Date: Fri, 13 Nov 2015 11:58:51 +0530
From: Kishon Vijay Abraham I <kishon@...com>
To: Heiko Stuebner <heiko@...ech.de>, <mturquette@...libre.com>,
<sboyd@...eaurora.org>
CC: <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>,
<linux-rockchip@...ts.infradead.org>, <dianders@...omium.org>,
<romain.perier@...il.com>, <arnd@...db.de>
Subject: Re: [PATCH 1/8] phy: rockchip-usb: fix clock get-put mismatch
Hi,
On Thursday 05 November 2015 03:14 AM, Heiko Stuebner wrote:
> Currently the phy driver only gets the optional clock reference but
> never puts it again, neither during error handling nor on remove.
> Fix that by moving the clk_put to a devm-action that gets called at
> the right time when all other devm actions are done.
>
> Signed-off-by: Heiko Stuebner <heiko@...ech.de>
> ---
> drivers/phy/phy-rockchip-usb.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/phy/phy-rockchip-usb.c b/drivers/phy/phy-rockchip-usb.c
> index 91d6f34..dfc056b 100644
> --- a/drivers/phy/phy-rockchip-usb.c
> +++ b/drivers/phy/phy-rockchip-usb.c
> @@ -90,6 +90,14 @@ static const struct phy_ops ops = {
> .owner = THIS_MODULE,
> };
>
> +static void rockchip_usb_phy_action(void *data)
> +{
> + struct rockchip_usb_phy *rk_phy = data;
> +
> + if (rk_phy->clk)
> + clk_put(rk_phy->clk);
> +}
> +
> static int rockchip_usb_phy_probe(struct platform_device *pdev)
> {
> struct device *dev = &pdev->dev;
> @@ -124,6 +132,13 @@ static int rockchip_usb_phy_probe(struct platform_device *pdev)
> if (IS_ERR(rk_phy->clk))
> rk_phy->clk = NULL;
>
> + err = devm_add_action(dev, rockchip_usb_phy_action, rk_phy);
> + if (err) {
> + if (rk_phy->clk)
> + clk_put(rk_phy->clk);
If devm_add_action is added before clk_get this check wouldn't be required at all.
Thanks
Kishon
--
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