From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [RFC PATCH 3/3] ARM: keystone: pm_domain: setup clk pm domain clocks from DT Date: Mon, 08 Sep 2014 13:47:59 -0700 Message-ID: <7hmwa9on40.fsf@linaro.org> References: <1406313096-29761-1-git-send-email-grygorii.strashko@ti.com> <1406313096-29761-4-git-send-email-grygorii.strashko@ti.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <1406313096-29761-4-git-send-email-grygorii.strashko@ti.com> (Grygorii Strashko's message of "Fri, 25 Jul 2014 21:31:36 +0300") Sender: linux-sh-owner@vger.kernel.org To: Grygorii Strashko Cc: santosh.shilimkar@ti.com, "Rafael J. Wysocki" , Geert Uytterhoeven , linux-pm@vger.kernel.org, ben.dooks@codethink.co.uk, laurent.pinchart@ideasonboard.com, grant.likely@secretlab.ca, ulf.hansson@linaro.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org List-Id: linux-pm@vger.kernel.org Grygorii Strashko 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