From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
<linux-media@vger.kernel.org>,
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH/RFC 1/9] clk: shmobile: r8a7795: Add FCP clocks
Date: Thu, 3 Mar 2016 00:17:54 +0000 [thread overview]
Message-ID: <87io14beqj.wl%kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <87d1rfj9n3.wl%kuninori.morimoto.gx@renesas.com>
Hi Laurent
> > > The parent clock isn't documented in the datasheet, use S2D1 as a best
> > > guess for now.
> >
> > Would you be able to find out what the parent clock is for the FCP and LVDS
> > (patch 2/9) clocks ?
It seems FCP clock is based on each SoC
In H3 ES1 case, it is using
- s2d2 (for 200MHz)
- s2d1 (for 400MHz)
next prev parent reply other threads:[~2016-03-03 0:17 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 [this message]
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
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=87io14beqj.wl%kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.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 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.