From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH/RFC 1/9] clk: shmobile: r8a7795: Add FCP clocks
Date: Thu, 03 Mar 2016 12:49:55 +0200 [thread overview]
Message-ID: <3162705.iiHBb2SECU@avalon> (raw)
In-Reply-To: <8737s8armo.wl%kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san,
On Thursday 03 March 2016 08:37:02 Kuninori Morimoto wrote:
> Hi Laurent
>
> >>>> - s2d2 (for 200MHz)
> >>>> - s2d1 (for 400MHz)
> >>>
> >>> Thank you for the information. Do you mean that different FCP instances
> >>> use different clocks ? If so, could you tell us which clock is used by
> >>> each instance in th H3 ES1 ?
> >>
> >> Sorry for my confusable mail.
> >> All FCP on H3 ES1 is using above,
> >> but, M3 or E3 will use different clock.
> >>
> >> Is this more clear ?
> >
> > Does it mean that every FCP instance uses both the S2D2 and the S2D1
> > clocks as functional clocks on H3 ES1 ?
>
> - s2d2 (200MHz) is for APB-IF,
> - s2d1 (400MHz) is for AXI-IF, and internal
>
> Is this clear answer ?
It is, thank you very much for putting up with my slow mind ;-)
Geert, deciding what clock to use as a parent for the MSTP clock becomes
interesting, As S2D2 clocks the control interface I propose picking it. This
shows the limits of the MSTP clock model though, MSTP is really a module stop
bit, not a clock.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2016-03-03 10:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 2:00 [PATCH/RFC 0/9] FCP support for Renesas video cores Laurent Pinchart
2016-02-12 2:00 ` [PATCH/RFC 1/9] clk: shmobile: r8a7795: Add FCP clocks Laurent Pinchart
2016-02-15 9:22 ` Geert Uytterhoeven
2016-02-15 12:26 ` Laurent Pinchart
2016-02-26 10:55 ` Laurent Pinchart
2016-03-01 1:03 ` Kuninori Morimoto
2016-03-03 0:17 ` Kuninori Morimoto
2016-03-03 6:52 ` Laurent Pinchart
2016-03-03 7:19 ` Kuninori Morimoto
2016-03-03 7:31 ` Laurent Pinchart
2016-03-03 8:37 ` Kuninori Morimoto
2016-03-03 10:49 ` Laurent Pinchart [this message]
2016-03-03 11:56 ` Geert Uytterhoeven
2016-03-03 12:04 ` Laurent Pinchart
2016-04-12 6:27 ` Kuninori Morimoto
2016-02-12 2:00 ` [PATCH/RFC 2/9] clk: shmobile: r8a7795: Add LVDS module clock Laurent Pinchart
2016-02-15 9:24 ` Geert Uytterhoeven
2016-02-15 12:27 ` Laurent Pinchart
2016-02-12 2:00 ` [PATCH/RFC 3/9] v4l: Add Renesas R-Car FCP driver Laurent Pinchart
2016-02-15 9:32 ` Geert Uytterhoeven
2016-02-15 12:35 ` Laurent Pinchart
2016-02-26 13:20 ` Geert Uytterhoeven
2016-02-12 2:00 ` [PATCH/RFC 4/9] v4l: vsp1: VSPD instances have no LUT on Gen3 Laurent Pinchart
2016-02-12 2:00 ` [PATCH/RFC 5/9] v4l: vsp1: Add FCP support Laurent Pinchart
2016-02-12 2:00 ` [PATCH/RFC 6/9] ARM64: renesas: r8a7795: Add FCPV nodes Laurent Pinchart
2016-02-15 9:45 ` Geert Uytterhoeven
2016-02-15 12:50 ` Laurent Pinchart
2016-02-12 2:00 ` [PATCH/RFC 7/9] ARM64: renesas: r8a7795: Add VSP instances Laurent Pinchart
2016-02-15 9:58 ` Geert Uytterhoeven
2016-02-15 12:53 ` Laurent Pinchart
2016-02-12 2:00 ` [PATCH/RFC 8/9] ARM64: renesas: r8a7795: Add DU device to DT Laurent Pinchart
2016-02-12 2:00 ` [PATCH/RFC 9/9] ARM64: renesas: salvator-x: Enable DU Laurent Pinchart
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=3162705.iiHBb2SECU@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert+renesas@glider.be \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.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).