From: <jiada_wang@mentor.com>
To: <broonie@kernel.org>, <perex@perex.cz>, <tiwai@suse.com>,
<kuninori.morimoto.gx@renesas.com>,
<vladimir_zapolskiy@mentor.com>
Cc: <alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH linux-next v2 1/6] clk: renesas: r8a7795: Add ADG clock
Date: Mon, 3 Dec 2018 20:21:55 +0900 [thread overview]
Message-ID: <20181203112200.18220-2-jiada_wang@mentor.com> (raw)
In-Reply-To: <20181203112200.18220-1-jiada_wang@mentor.com>
From: Takeshi Kihara <takeshi.kihara.df@renesas.com>
This patch adds ADG clock to the R8A7795 SoC.
Signed-off-by: Takeshi Kihara <takeshi.kihara.df@renesas.com>
Signed-off-by: Jiada Wang <jiada_wang@mentor.com>
---
drivers/clk/renesas/r8a7795-cpg-mssr.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/renesas/r8a7795-cpg-mssr.c b/drivers/clk/renesas/r8a7795-cpg-mssr.c
index 119c02440726..813288099c84 100644
--- a/drivers/clk/renesas/r8a7795-cpg-mssr.c
+++ b/drivers/clk/renesas/r8a7795-cpg-mssr.c
@@ -237,6 +237,7 @@ static struct mssr_mod_clk r8a7795_mod_clks[] __initdata = {
DEF_MOD("can-if0", 916, R8A7795_CLK_S3D4),
DEF_MOD("i2c6", 918, R8A7795_CLK_S0D6),
DEF_MOD("i2c5", 919, R8A7795_CLK_S0D6),
+ DEF_MOD("adg", 922, R8A7795_CLK_S0D1),
DEF_MOD("i2c-dvfs", 926, R8A7795_CLK_CP),
DEF_MOD("i2c4", 927, R8A7795_CLK_S0D6),
DEF_MOD("i2c3", 928, R8A7795_CLK_S0D6),
--
2.17.0
next prev parent reply other threads:[~2018-12-03 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 11:21 [PATCH linux-next v2 0/6] clk: renesas: adg: add AVB Clock jiada_wang
2018-12-03 11:21 ` jiada_wang [this message]
2018-12-03 11:21 ` [PATCH linux-next v2 2/6] clk: renesas: r8a7796: Add ADG clock jiada_wang
2018-12-03 11:21 ` [PATCH linux-next v2 3/6] clk: renesas: r8a77990: Add ADG clocks jiada_wang
2018-12-03 11:21 ` [PATCH linux-next v2 4/6] clk: renesas: r8a77995: Add ADG clock jiada_wang
2018-12-03 12:11 ` [PATCH linux-next v2 0/6] clk: renesas: adg: add AVB Clock Vladimir Zapolskiy
2018-12-04 8:24 ` Jiada Wang
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=20181203112200.18220-2-jiada_wang@mentor.com \
--to=jiada_wang@mentor.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=vladimir_zapolskiy@mentor.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).