From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: alexandre.belloni@bootlin.com,
Michael Turquette <mturquette@baylibre.com>,
thierry.reding@gmail.com, lee.jones@linaro.org,
linux-clk@vger.kernel.org, linux-rtc@vger.kernel.org,
Ludovic.Desroches@microchip.com, o.rempel@pengutronix.de,
andy.shevchenko@gmail.com, aardelean@deviqon.com,
linux-pwm@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
broonie@kernel.org, Jonathan.Cameron@huawei.com,
linux-arm-kernel@lists.infradead.org, a.zummo@towertech.it,
Stephen Boyd <sboyd@kernel.org>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
wsa@kernel.org, kernel@pengutronix.de, akpm@linux-foundation.org,
torvalds@linux-foundation.org, Claudiu.Beznea@microchip.com
Subject: Re: About clk maintainership [Was: Re: [PULL] Add variants of devm_clk_get for prepared and enabled clocks enabled clocks]
Date: Mon, 2 Aug 2021 17:38:24 +0100 [thread overview]
Message-ID: <20210802163824.GK22278@shell.armlinux.org.uk> (raw)
In-Reply-To: <20210802152755.ibisunvibmwhiyry@pengutronix.de>
On Mon, Aug 02, 2021 at 05:27:55PM +0200, Uwe Kleine-König wrote:
> Hello Russell,
>
> On Mon, Aug 02, 2021 at 10:48:10AM +0100, Russell King (Oracle) wrote:
> > I think devm_clk_get() should not be part of CCF but should be
> > part of the interface level - it's silly to have devm_clk_get()
> > being CCF but not clk_get(). The same should go for the other
> > devm wrappers around the plain clk_* interfaces.
>
> What is the practical difference between "Function X is part of CCF" and
> "Function X is part of the clk interface and there is only CCF who
> implements it"?
clkdev is maintained by me as part of the API, and provides clk_get()
functionality for all clk implementations. To then have devm_clk_get(),
which merely provides a wrapper around clk_get() adding the devm
semantics being part of CCF is not sane - devm_clk_get() isn't
specific to CCF or in fact any clk API implementation.
> > There have been several different approaches to wrapping things up,
> > but here's a question: should we make it easier to do the lazy thing
> > (get+enable) or should we make it easier to be power efficient?
> > Shouldn't we be encouraging people to write power efficient drivers?
>
> Yeah, sounds compelling, but I wonder if that's of practical importance.
> How many driver authors do you expect to lure into making a better
> driver just because devm_clk_get_prepared() doesn't exist? In contrast:
> How many drivers become simpler with devm_clk_get_prepared() and so
> it becomes easier to maintain them and easier to spot bugs?
> In the absence of devm_clk_get_prepared(), is it better that several
> frameworks (or drivers) open code it?
It probably depends on where you stand on power management and power
efficiency issues. Personally, I would like to see more effort put
into drivers to make them more power efficient, and I believe in the
coming years, power efficiency is going to become a big issue.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2021-08-02 16:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210510174142.986250-1-u.kleine-koenig@pengutronix.de>
[not found] ` <20210609202123.u5rmw7al4x3rrvun@pengutronix.de>
[not found] ` <20210625171434.3xusxpxjprcdqa47@pengutronix.de>
[not found] ` <20210705080144.zfbzkm7l3gmnh6st@pengutronix.de>
[not found] ` <20210722060654.nudpdtemosi64nlb@pengutronix.de>
[not found] ` <YPkg0wtYIoHKpTUW@kunai>
[not found] ` <20210722081817.2tsjzof4gvldq6ka@pengutronix.de>
[not found] ` <YPlfcbkxiBmB+vw1@kunai>
[not found] ` <CAHp75VfC=s12Unw3+Cn0ag71mM5i90=Jbwj4nYwB5cPKiUTRSA@mail.gmail.com>
2021-07-23 9:13 ` [PULL] Add variants of devm_clk_get for prepared and enabled clocks enabled clocks Uwe Kleine-König
2021-07-26 9:18 ` Claudiu.Beznea
2021-07-26 9:52 ` Andy Shevchenko
2021-07-26 12:32 ` Wolfram Sang
2021-07-26 13:28 ` Andy Shevchenko
2021-07-26 17:40 ` Wolfram Sang
2021-07-28 20:25 ` About clk maintainership [Was: Re: [PULL] Add variants of devm_clk_get for prepared and enabled clocks enabled clocks] Uwe Kleine-König
2021-07-28 20:40 ` Russell King (Oracle)
2021-07-31 7:41 ` Stephen Boyd
2021-07-31 8:07 ` Andy Shevchenko
2021-07-31 12:00 ` Uwe Kleine-König
2021-08-02 9:36 ` Jonathan Cameron
2021-08-02 9:48 ` Russell King (Oracle)
2021-08-02 15:27 ` Uwe Kleine-König
2021-08-02 16:38 ` Russell King (Oracle) [this message]
2021-08-02 17:13 ` Andy Shevchenko
2021-08-02 20:28 ` Russell King (Oracle)
2021-08-03 8:11 ` Stephen Boyd
2021-08-03 10:40 ` Uwe Kleine-König
2021-08-06 0:26 ` Stephen Boyd
2021-09-14 13:22 ` Uwe Kleine-König
2021-09-14 13:52 ` Mark Brown
2021-08-03 7:44 ` Stephen Boyd
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=20210802163824.GK22278@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Claudiu.Beznea@microchip.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=a.zummo@towertech.it \
--cc=aardelean@deviqon.com \
--cc=akpm@linux-foundation.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=kernel@pengutronix.de \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=o.rempel@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wsa@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;
as well as URLs for NNTP newsgroup(s).