linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Biju Das <biju.das@bp.renesas.com>
To: Simon Horman <horms+renesas@verge.net.au>,
	Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	"linux-renesas-soc@vger.kernel.org" 
	<linux-renesas-soc@vger.kernel.org>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Subject: RE: [PATCH/RFT v2 5/6] clk: renesas: rcar-gen3: Support r8a7745 Z2 clock divider
Date: Wed, 30 Jan 2019 09:43:31 +0000	[thread overview]
Message-ID: <OSBPR01MB21036AEED543FE6DD9001E0CB8900@OSBPR01MB2103.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20190130094029.9604-6-horms+renesas@verge.net.au>

Hi Simon,

Thanks for the patch

> Subject: [PATCH/RFT v2 5/6] clk: renesas: rcar-gen3: Support r8a7745 Z2 clock
> divider
>
> On the RZ/G2E (r8a7745) SoC the Z2FC bits of the RFQCRC register, which
> control the frequency division ratio for the Z2φ clock are located at bit[12:8]
> rather than the more common location bit[4:0].
>
> This change is made with reference to the User's Manual v0.61.
>
> Fixes: 9127d54bb894 ("clk: renesas: cpg-mssr: Add R8A7745 support")
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> ---
>  drivers/clk/renesas/rcar-gen3-cpg.c | 4 ++++
>  1 file changed, 4 insertions(+)
>
> diff --git a/drivers/clk/renesas/rcar-gen3-cpg.c b/drivers/clk/renesas/rcar-
> gen3-cpg.c
> index d21fdeb520e1..dfd2b9caeaf5 100644
> --- a/drivers/clk/renesas/rcar-gen3-cpg.c
> +++ b/drivers/clk/renesas/rcar-gen3-cpg.c
> @@ -450,6 +450,10 @@ static const struct soc_device_attribute
> cpg_quirks_match[] __initconst = {
>  .soc_id = "r8a77990",
>  .data = (void *)Z2FC_BIT_MASK_SFT_8,
>  },
> +{
> +.soc_id = "r8a7745",
> +.data = (void *)Z2FC_BIT_MASK_SFT_8,
> +},
>  { /* sentinel */ }
>  };


RZ/G2E  SoC id is r8a774c0.

Regards,
Biju



Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.

  reply	other threads:[~2019-01-30  9:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30  9:40 [PATCH v2 0/6] clk: renesas: r8a77990: Add Z2 clock Simon Horman
2019-01-30  9:40 ` [PATCH v2 1/6] clk: renesas: rcar-gen3: Parameterise Z and Z2 clock fixed divisor Simon Horman
2019-01-30  9:40 ` [PATCH v2 2/6] clk: renesas: rcar-gen3: Support r8a77990 Z2 clock divider Simon Horman
2019-01-30  9:40 ` [PATCH v2 3/6] clk: renesas: rcar-gen3: Support Z and Z2 clocks with high frequency parents Simon Horman
2019-01-30  9:40 ` [PATCH v2 4/6] clk: renesas: r8a77990: Add Z2 clock Simon Horman
2019-01-30  9:40 ` [PATCH/RFT v2 5/6] clk: renesas: rcar-gen3: Support r8a7745 Z2 clock divider Simon Horman
2019-01-30  9:43   ` Biju Das [this message]
2019-01-30 10:10     ` Simon Horman
2019-01-30 18:51     ` Fabrizio Castro
2019-01-30  9:40 ` [PATCH/RFT v2 6/6] clk: renesas: r8a7745: Implement Z2 as a variable clock Simon Horman
2019-01-30  9:46   ` Biju Das
2019-01-30 10:11     ` Simon Horman
2019-01-30 18:43   ` Fabrizio Castro

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=OSBPR01MB21036AEED543FE6DD9001E0CB8900@OSBPR01MB2103.jpnprd01.prod.outlook.com \
    --to=biju.das@bp.renesas.com \
    --cc=fabrizio.castro@bp.renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@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).