From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Phil Edworthy <phil.edworthy@renesas.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Simon Horman <horms@verge.net.au>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 0/2] clk: Add functions to get optional clocks
Date: Fri, 31 Aug 2018 21:23:28 +0300 [thread overview]
Message-ID: <20180831182328.GF11447@smile.fi.intel.com> (raw)
In-Reply-To: <1535724443-21150-1-git-send-email-phil.edworthy@renesas.com>
On Fri, Aug 31, 2018 at 03:07:21PM +0100, Phil Edworthy wrote:
> 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.
>
Looks good to me
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Perhaps, you may convert 8250_dw to this one later on as an example...
> Phil Edworthy (2):
> clk: Add of_clk_get_by_name_optional() function
> clk: Add functions to get optional clocks
>
> drivers/clk/clk-devres.c | 18 ++++++++++--
> drivers/clk/clkdev.c | 74 ++++++++++++++++++++++++++++++++++++++----------
> include/linux/clk.h | 35 +++++++++++++++++++++++
> 3 files changed, 110 insertions(+), 17 deletions(-)
>
> --
> 2.7.4
>
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2018-08-31 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 14:07 [PATCH v5 0/2] clk: Add functions to get optional clocks Phil Edworthy
2018-08-31 14:07 ` [PATCH v5 1/2] clk: Add of_clk_get_by_name_optional() function Phil Edworthy
2018-09-01 2:45 ` Stephen Boyd
2018-09-03 9:32 ` Phil Edworthy
2018-09-03 13:21 ` Phil Edworthy
2018-11-13 19:44 ` Stephen Boyd
2018-08-31 14:07 ` [PATCH v5 2/2] clk: Add functions to get optional clocks Phil Edworthy
2018-09-01 11:43 ` kbuild test robot
2018-09-01 16:01 ` kbuild test robot
2018-08-31 18:23 ` Andy Shevchenko [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=20180831182328.GF11447@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--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=phil.edworthy@renesas.com \
--cc=sboyd@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).