From: Chris Paterson <Chris.Paterson2@renesas.com>
To: Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Biju Das <biju.das@bp.renesas.com>
Subject: RE: [PATCH] clk: renesas: r8a774a1: Fix LAST_DT_CORE_CLK
Date: Fri, 22 Feb 2019 12:01:21 +0000 [thread overview]
Message-ID: <TYAPR01MB2285B3DDEA95F441338DF14AB77F0@TYAPR01MB2285.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <1550836779-6868-1-git-send-email-fabrizio.castro@bp.renesas.com>
> From: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
> Sent: 22 February 2019 12:00
>
> Enum LAST_DT_CORE_CLK needs updating as R8A774A1_CLK_CANFD
> was recently added and it's the core clock with the highest
> index.
>
> Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Reviewed-by: Chris Paterson <chris.paterson2@renesas.com>
> ---
> drivers/clk/renesas/r8a774a1-cpg-mssr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clk/renesas/r8a774a1-cpg-mssr.c
> b/drivers/clk/renesas/r8a774a1-cpg-mssr.c
> index 5fcd6c5..8e7bb43 100644
> --- a/drivers/clk/renesas/r8a774a1-cpg-mssr.c
> +++ b/drivers/clk/renesas/r8a774a1-cpg-mssr.c
> @@ -21,7 +21,7 @@
>
> enum clk_ids {
> /* Core Clock Outputs exported to DT */
> - LAST_DT_CORE_CLK = R8A774A1_CLK_OSC,
> + LAST_DT_CORE_CLK = R8A774A1_CLK_CANFD,
>
> /* External Input Clocks */
> CLK_EXTAL,
> --
> 2.7.4
next prev parent reply other threads:[~2019-02-22 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 11:59 [PATCH] clk: renesas: r8a774a1: Fix LAST_DT_CORE_CLK Fabrizio Castro
2019-02-22 12:01 ` Chris Paterson [this message]
2019-02-25 9:27 ` Simon Horman
2019-02-25 9:32 ` Geert Uytterhoeven
2019-02-25 9:44 ` Fabrizio Castro
2019-02-25 9:47 ` Geert Uytterhoeven
2019-02-25 9:49 ` Fabrizio Castro
2019-02-25 17:13 ` 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=TYAPR01MB2285B3DDEA95F441338DF14AB77F0@TYAPR01MB2285.jpnprd01.prod.outlook.com \
--to=chris.paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.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).