From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Jon Hunter <jonathanh@nvidia.com>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-tegra@vger.kernel.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH V4] PM / clk: Add support for obtaining clocks from device-tree
Date: Fri, 18 Mar 2016 01:46:17 +0100 [thread overview]
Message-ID: <1724113.VnPWaRLGz3@vostro.rjw.lan> (raw)
In-Reply-To: <CAMuHMdV_PVnZ11BJ3FHe9Gc5nH-yk1u-NuHntOnRiQ4npVkd8g@mail.gmail.com>
On Tuesday, March 15, 2016 01:15:16 PM Geert Uytterhoeven wrote:
> On Tue, Mar 15, 2016 at 12:33 PM, Jon Hunter <jonathanh@nvidia.com> wrote:
> > The PM clocks framework requires clients to pass either a con-id or a
> > valid clk pointer in order to add a clock to a device. Add a new
> > function of_pm_clk_add_clks() to allows device clocks to be retrieved
> > from device-tree and populated for a given device. Note that it is
> > not necessary to make the compilation of this new function dependent
> > upon CONFIG_OF because there are stubs functions for the device-tree
> > APIs used.
> >
> > In order to handle errors encountered when adding clocks from
> > device-tree, add a function pm_clk_remove_clk() to remove any clocks
> > (using a pointer to the clk structure) that have been added
> > successfully before the error occurred.
> >
> > Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
>
> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
Applied.
Thanks,
Rafael
prev parent reply other threads:[~2016-03-18 0:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 11:33 [PATCH V4] PM / clk: Add support for obtaining clocks from device-tree Jon Hunter
2016-03-15 12:15 ` Geert Uytterhoeven
2016-03-18 0:46 ` Rafael J. Wysocki [this message]
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=1724113.VnPWaRLGz3@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox