From: Stephen Boyd <sboyd@codeaurora.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Alexandre Courbot <gnurou@gmail.com>,
Jon Hunter <jonathanh@nvidia.com>,
linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2] clk: tegra: Add BPMP clock driver
Date: Fri, 3 Feb 2017 12:43:02 -0800 [thread overview]
Message-ID: <20170203204302.GF25384@codeaurora.org> (raw)
In-Reply-To: <20170125074112.GC13025@ulmo.ba.sec>
On 01/25, Thierry Reding wrote:
> On Thu, Nov 17, 2016 at 04:47:31PM +0100, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > This driver uses the services provided by the BPMP firmware driver to
> > implement a clock driver based on the MRQ_CLK request. This part of the
> > BPMP ABI provides a means to enumerate and control clocks and should
> > allow the driver to work on any chip that supports this ABI.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> > Changes in v2:
> > - rename ->prepare() and ->unprepare() implementations for consistency
> > - implement ->is_prepared() instead of ->is_enabled() to avoid the need
> > for atomic operations
> > - rename tegra_bpmp_clk_message.clk member to id
> > - remove a double semi-colon and a stray ampersand
> > - drop extra check for validity of parent index, the core does it
> > already
> > - make struct tegra_bpmp carry an array of struct tegra_bpmp_clk instead
> > of struct clk_hw to simplify some driver code
> > - zero out struct clk_init_data to avoid potentially uninitialized data
> > - use devm_clk_hw_register() instead of clk_register() because we never
> > need the opaque struct clk cookie
> > - rearrange functions so that they appear in the order specified by
> > struct clk_ops
> >
> > drivers/clk/tegra/Kconfig | 4 +
> > drivers/clk/tegra/Makefile | 1 +
> > drivers/clk/tegra/clk-bpmp.c | 620 +++++++++++++++++++++++++++++++++++++++++++
> > 3 files changed, 625 insertions(+)
> > create mode 100644 drivers/clk/tegra/clk-bpmp.c
>
> Stephen, Mike,
>
> we missed the last merge window with this, but it would be nice to get
> it in this time. Any more comments?
>
Don't think so. Shall I merge it into clk-next?
Sadly it's not easy to test compile this single driver on the
commandline. Grumble.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-02-03 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 16:11 [PATCH v4] clk: tegra: Add BPMP clock driver Thierry Reding
2016-11-17 1:19 ` Stephen Boyd
2016-11-17 9:58 ` Thierry Reding
2016-11-17 15:57 ` Thierry Reding
2016-11-17 15:47 ` [PATCH v2] " Thierry Reding
2017-01-25 7:41 ` Thierry Reding
2017-02-03 20:43 ` Stephen Boyd [this message]
2017-02-06 11:13 ` Thierry Reding
2017-02-06 22:52 ` Stephen Boyd
2017-02-07 10:52 ` Thierry Reding
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=20170203204302.GF25384@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
/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).