[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170130185551.GM8801@codeaurora.org>
Date: Mon, 30 Jan 2017 10:55:51 -0800
From: Stephen Boyd <sboyd@...eaurora.org>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Russell King - ARM Linux <linux@...linux.org.uk>,
Guenter Roeck <linux@...ck-us.net>,
Michael Turquette <mturquette@...libre.com>,
Viresh Kumar <viresh.kumar@...aro.org>,
Andy Shevchenko <andy.shevchenko@...il.com>,
linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] clk: add more managed APIs
On 01/29, Dmitry Torokhov wrote:
> When converting a driver to managed resources it is desirable to be able to
> manage all resources in the same fashion. This change allows managing
> clocks in the same way we manage many other resources.
Can you please add 'managing clock prepared and enabled state in
the same way'?
The current wording makes it sound like we don't have
devm_clk_get() when we do.
>
> This adds the following managed APIs:
>
> - devm_clk_prepare()/devm_clk_unprepare();
> - devm_clk_prepare_enable()/devm_clk_disable_unprepare().
Wouldn't this be preceded by a devm_clk_get() call? Wouldn't it
be even shorter to have the APIs
devm_clk_get_and_prepare()/devm_clk_unprepare_and_put()
devm_clk_get_and_prepare_enable()/devm_clk_disable_unprepare_and_put()
instead?
Is there any other subsystem that has similar functionality?
Regulators? GPIOs? Resets? I'm just curious if those subsystems
also need similar changes.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
Powered by blists - more mailing lists