All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>
Cc: Peter De Schrijver <pdeschrijver@nvidia.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: [PATCH 2/4] clk: tegra: Add peripheral clock registration helper
Date: Fri,  1 Sep 2017 16:53:41 +0200	[thread overview]
Message-ID: <20170901145343.19890-2-thierry.reding@gmail.com> (raw)
In-Reply-To: <20170901145343.19890-1-thierry.reding@gmail.com>

From: Thierry Reding <treding@nvidia.com>

There is a common pattern that registers individual peripheral clocks
from an initialization table. Add a common implementation to remove the
duplication from various call sites.

Signed-off-by: Thierry Reding <treding@nvidia.com>
---
 drivers/clk/tegra/clk-periph.c | 8 ++++++++
 drivers/clk/tegra/clk.h        | 3 +++
 2 files changed, 11 insertions(+)

diff --git a/drivers/clk/tegra/clk-periph.c b/drivers/clk/tegra/clk-periph.c
index cf80831de79d..9475c00b7cf9 100644
--- a/drivers/clk/tegra/clk-periph.c
+++ b/drivers/clk/tegra/clk-periph.c
@@ -203,3 +203,11 @@ struct clk *tegra_clk_register_periph_nodiv(const char *name,
 	return _tegra_clk_register_periph(name, parent_names, num_parents,
 			periph, clk_base, offset, CLK_SET_RATE_PARENT);
 }
+
+struct clk *tegra_clk_register_periph_data(void __iomem *clk_base,
+					   struct tegra_periph_init_data *init)
+{
+	return _tegra_clk_register_periph(init->name, init->p.parent_names,
+					  init->num_parents, &init->periph,
+					  clk_base, init->offset, init->flags);
+}
diff --git a/drivers/clk/tegra/clk.h b/drivers/clk/tegra/clk.h
index 872f1189ad7f..3b2763df51c2 100644
--- a/drivers/clk/tegra/clk.h
+++ b/drivers/clk/tegra/clk.h
@@ -662,6 +662,9 @@ struct tegra_periph_init_data {
 			_clk_num, _gate_flags, _clk_id,\
 			NULL, 0, NULL)
 
+struct clk *tegra_clk_register_periph_data(void __iomem *clk_base,
+					   struct tegra_periph_init_data *init);
+
 /**
  * struct clk_super_mux - super clock
  *
-- 
2.13.3

  reply	other threads:[~2017-09-01 14:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01 14:53 [PATCH 1/4] dt-bindings: clock: tegra: Add sor1_out clock Thierry Reding
2017-09-01 14:53 ` Thierry Reding
2017-09-01 14:53 ` Thierry Reding [this message]
2017-11-02  8:16   ` [PATCH 2/4] clk: tegra: Add peripheral clock registration helper Stephen Boyd
2017-11-02  8:16     ` Stephen Boyd
2017-09-01 14:53 ` [PATCH 3/4] clk: tegra: Use tegra_clk_register_periph_data() Thierry Reding
2017-09-01 14:53   ` Thierry Reding
2017-11-02  8:16   ` Stephen Boyd
2017-11-02  8:16     ` Stephen Boyd
2017-09-01 14:53 ` [PATCH 4/4] clk: tegra: Fix sor1_out clock implementation Thierry Reding
2017-09-01 14:53   ` Thierry Reding
2017-11-02  8:16   ` Stephen Boyd
2017-11-02  8:16 ` [PATCH 1/4] dt-bindings: clock: tegra: Add sor1_out clock Stephen Boyd
2017-11-02  8:16   ` Stephen Boyd
2017-11-02  8:46   ` Thierry Reding
2017-11-02  8:46     ` Thierry Reding
2017-11-03 15:16     ` Stephen Boyd
2017-11-03 15:16       ` 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=20170901145343.19890-2-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=pdeschrijver@nvidia.com \
    --cc=sboyd@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.