[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMP44s0h+6XTaJv8q-MJe4vmDiBzNG2cjTugSn7nFyAsZPk+Ag@mail.gmail.com>
Date: Thu, 22 Nov 2012 03:47:31 +0100
From: Felipe Contreras <felipe.contreras@...il.com>
To: Omar Ramirez Luna <omar.luna@...aro.org>
Cc: Tony Lindgren <tony@...mide.com>, Joerg Roedel <joro@...tes.org>,
Russell King <linux@....linux.org.uk>,
Ohad Ben-Cohen <ohad@...ery.com>, Ido Yariv <ido@...ery.com>,
Mauro Carvalho Chehab <mchehab@...hat.com>,
Paul Walmsley <paul@...an.com>, linux-omap@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
iommu@...ts.linux-foundation.org, Kevin Hilman <khilman@...com>
Subject: Re: [PATCH v5 4/5] iommu/omap: adapt to runtime pm
On Tue, Nov 20, 2012 at 2:05 AM, Omar Ramirez Luna <omar.luna@...aro.org> wrote:
> @@ -1022,7 +1019,8 @@ static int __devexit omap_iommu_remove(struct platform_device *pdev)
> release_mem_region(res->start, resource_size(res));
> iounmap(obj->regbase);
>
> - clk_put(obj->clk);
> + pm_runtime_disable(obj->dev);
> +
> dev_info(&pdev->dev, "%s removed\n", obj->name);
> kfree(obj);
> return 0;
I still believe this is not needed. The device framework does that
when removing the device, and does it more properly, with
__pm_runtime_disable(dev, false).
Cheers.
--
Felipe Contreras
--
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