From: Kevin Hilman <khilman@kernel.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 3/3] ARM: keystone: pm_domain: setup clk pm domain clocks from DT
Date: Mon, 08 Sep 2014 20:47:59 +0000 [thread overview]
Message-ID: <7hmwa9on40.fsf@linaro.org> (raw)
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")
Grygorii Strashko <grygorii.strashko@ti.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
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@kernel.org>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: <santosh.shilimkar@ti.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Geert Uytterhoeven <geert+renesas@glider.be>,
<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>
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 [thread overview]
Message-ID: <7hmwa9on40.fsf@linaro.org> (raw)
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")
Grygorii Strashko <grygorii.strashko@ti.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
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@kernel.org>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: santosh.shilimkar@ti.com, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Geert Uytterhoeven <geert+renesas@glider.be>,
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
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 [thread overview]
Message-ID: <7hmwa9on40.fsf@linaro.org> (raw)
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")
Grygorii Strashko <grygorii.strashko@ti.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
WARNING: multiple messages have this Message-ID (diff)
From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 3/3] ARM: keystone: pm_domain: setup clk pm domain clocks from DT
Date: Mon, 08 Sep 2014 13:47:59 -0700 [thread overview]
Message-ID: <7hmwa9on40.fsf@linaro.org> (raw)
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")
Grygorii Strashko <grygorii.strashko@ti.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
next prev parent reply other threads:[~2014-09-08 20:47 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 17:47 [RFC PATCH 0/3] PM / clock_ops: allow to specify custom pm_clk_notifier callback Grygorii Strashko
2014-07-25 18:31 ` Grygorii Strashko
2014-07-25 18:31 ` Grygorii Strashko
2014-07-25 18:31 ` Grygorii Strashko
2014-07-25 17:46 ` [RFC PATCH 2/3] " Grygorii Strashko
2014-07-25 18:31 ` Grygorii Strashko
2014-07-25 18:31 ` Grygorii Strashko
2014-07-25 18:31 ` Grygorii Strashko
2014-07-25 17:47 ` [RFC PATCH 3/3] ARM: keystone: pm_domain: setup clk pm domain clocks from DT Grygorii Strashko
2014-07-25 18:31 ` Grygorii Strashko
2014-07-25 18:31 ` Grygorii Strashko
2014-07-25 18:31 ` Grygorii Strashko
2014-09-08 20:47 ` Kevin Hilman [this message]
2014-09-08 20:47 ` Kevin Hilman
2014-09-08 20:47 ` Kevin Hilman
2014-09-08 20:47 ` Kevin Hilman
2014-07-25 17:47 ` [RFC PATCH 1/3] PM / clock_ops: Add pm_clk_add_clk() Grygorii Strashko
2014-07-25 18:31 ` Grygorii Strashko
2014-07-25 18:31 ` Grygorii Strashko
2014-07-25 18:31 ` Grygorii Strashko
2014-09-08 21:37 ` [RFC PATCH 0/3] PM / clock_ops: allow to specify custom pm_clk_notifier callback Kevin Hilman
2014-09-08 21:37 ` Kevin Hilman
2014-09-08 21:37 ` Kevin Hilman
2014-09-08 21:37 ` Kevin Hilman
2014-09-09 13:41 ` Grygorii Strashko
2014-09-09 13:41 ` Grygorii Strashko
2014-09-09 13:41 ` Grygorii Strashko
2014-09-09 13:41 ` Grygorii Strashko
2014-09-10 12:34 ` Geert Uytterhoeven
2014-09-10 12:34 ` Geert Uytterhoeven
2014-09-10 12:34 ` Geert Uytterhoeven
2014-09-10 12:34 ` Geert Uytterhoeven
2014-09-17 15:03 ` Geert Uytterhoeven
2014-09-17 15:03 ` Geert Uytterhoeven
2014-09-17 15:03 ` Geert Uytterhoeven
2014-09-17 15:03 ` Geert Uytterhoeven
2014-09-17 16:04 ` Grygorii Strashko
2014-09-17 16:04 ` Grygorii Strashko
2014-09-17 16:04 ` Grygorii Strashko
2014-09-17 16:04 ` Grygorii Strashko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7hmwa9on40.fsf@linaro.org \
--to=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.