From: Phil Edworthy <phil.edworthy@renesas.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Russell King <linux@armlinux.org.uk>
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Phil Edworthy" <phil.edworthy@renesas.com>
Subject: [PATCH v9 0/2] clk: Add functions to get optional clocks
Date: Mon, 3 Dec 2018 11:13:07 +0000 [thread overview]
Message-ID: <20181203111309.3709-1-phil.edworthy@renesas.com> (raw)
Quite a few drivers get an optional clock, e.g. a bus clock required to
access peripheral's registers that is always enabled on some devices.
v9:
- Add a separate patch to add a comment about __of_clk_get_by_name() error
values.
- Add brackets after devm_clk_get so people know it's a function.
- Add kernel doc for clk_get_optional().
Phil Edworthy (2):
clk: Add comment about __of_clk_get_by_name() error values
clk: Add (devm_)clk_get_optional() functions
drivers/clk/clk-devres.c | 11 +++++++++++
drivers/clk/clkdev.c | 6 ++++++
include/linux/clk.h | 36 ++++++++++++++++++++++++++++++++++++
3 files changed, 53 insertions(+)
--
2.17.1
next reply other threads:[~2018-12-03 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 11:13 Phil Edworthy [this message]
2018-12-03 11:13 ` [PATCH v9 1/2] clk: Add comment about __of_clk_get_by_name() error values Phil Edworthy
2018-12-03 13:30 ` Andy Shevchenko
2018-12-06 12:30 ` Phil Edworthy
2019-01-16 15:18 ` Phil Edworthy
2019-01-24 21:07 ` Andy Shevchenko
2018-12-03 11:13 ` [PATCH v9 2/2] clk: Add (devm_)clk_get_optional() functions Phil Edworthy
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=20181203111309.3709-1-phil.edworthy@renesas.com \
--to=phil.edworthy@renesas.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).