[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7hmwa9on40.fsf@linaro.org>
Date: Mon, 08 Sep 2014 13:47:59 -0700
From: Kevin Hilman <khilman@...nel.org>
To: Grygorii Strashko <grygorii.strashko@...com>
Cc: <santosh.shilimkar@...com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Geert Uytterhoeven <geert+renesas@...der.be>,
<linux-pm@...r.kernel.org>, <ben.dooks@...ethink.co.uk>,
<laurent.pinchart@...asonboard.com>, <grant.likely@...retlab.ca>,
<ulf.hansson@...aro.org>, <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <linux-sh@...r.kernel.org>
Subject: Re: [RFC PATCH 3/3] ARM: keystone: pm_domain: setup clk pm domain clocks from DT
Grygorii Strashko <grygorii.strashko@...com> writes:
> This patch implements custom pm_clk_notifier callback for Keystone 2
> CLK PM domain which fills list of clocks for Device with all
> clocks assigned to this Device in DT.
>
> After this patch .con_ids field in pm_clk_notifier_block is not
> used and there are no limitation for clocks names in DT any more.
OK, but this also assumes you want *every* clock associated with a
device node managed by runtime PM. Is that really what you want?
I may have misunderstood, but your previous attempts at solving this
problem suggest you wanted finer grained control over which device
clocks are runtime PM managed and which ones arent.
Kevin
--
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