From: jamesjj.liao@mediatek.com (James Liao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 7/9] clk: mediatek: Add subsystem clocks of MT8173
Date: Thu, 6 Aug 2015 16:23:51 +0800 [thread overview]
Message-ID: <1438849431.27884.9.camel@mtksdaap41> (raw)
In-Reply-To: <20150805064605.GZ18700@pengutronix.de>
Hi Sascha,
On Wed, 2015-08-05 at 08:46 +0200, Sascha Hauer wrote:
> On Tue, Aug 04, 2015 at 04:16:56PM +0800, James Liao wrote:
> > static const struct mtk_fixed_clk fixed_clks[] __initconst = {
> > FIXED_CLK(CLK_TOP_CLKPH_MCK_O, "clkph_mck_o", "clk26m", 400 * MHZ),
> > FIXED_CLK(CLK_TOP_USB_SYSPLL_125M, "usb_syspll_125m", "clk26m", 125 * MHZ),
> > + FIXED_CLK(CLK_TOP_DSI0_DIG, "dsi0_dig", "clk26m", 130 * MHZ),
> > + FIXED_CLK(CLK_TOP_DSI1_DIG, "dsi1_dig", "clk26m", 130 * MHZ),
> > + FIXED_CLK(CLK_TOP_LVDS_PXL, "lvds_pxl", "lvdspll", 148.5 * MHZ),
> > + FIXED_CLK(CLK_TOP_LVDS_CTS, "lvds_cts", "lvdspll", 51.975 * MHZ),
>
> I would expect 51975 * KHZ here to avoid fractional numbers. Probably
> gcc calculates that during compile time so this will work as expected,
> still I'm not sure this is good style to use fractional numbers here.
As I know all constants will be calculated in compile time, so there
should be no difference between 51.975 * MHZ and 51975 * KHz.
> Anyway, on my system lvdspll is running at 150MHz. Are you sure there is
> a clock derived from this running at 148.5MHz? Is it really correct to
> use a fixed clock here or should it rather be lvdspll directly?
Here is the clock hierarchy between lvdspll and lvds_pxl:
-------- AD_VPLL_DPIX_CK -------- lvds_pxl -----
| |--------------------->| |---------->|
| | | cksys | |
LVDSPLL -->| LVDSTX | | buffer | | MMSYS
| | AD_LVDSTX_CLKDIG_CTS | test | lvds_cts |
| |--------------------->| |---------->|
-------- -------- -----
Some clocks and blocks are not modeled into CCF. But we prefer to enable
lvdspll before enabling lvds_pxl. So I modeled lvds_pxl (and lvds_cts)
as a fixed-rate clock with a source from lvdspll.
The frequency of these fixed-rate clocks (such as 148.5 MHz) are typical
rate. In fact, we don't care about the actual rate of these clocks. We
just care about the enable / disable sequence of them.
Best regards,
James
next prev parent reply other threads:[~2015-08-06 8:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 8:16 [PATCH v6 0/9] Fixes and new clocks support for Mediatek MT8173 James Liao
2015-08-04 8:16 ` [PATCH v6 1/9] clk: mediatek: Removed unused dpi_ck clock from MT8173 James Liao
2015-08-04 8:16 ` [PATCH v6 2/9] clk: mediatek: Remove unused code " James Liao
2015-08-04 8:16 ` [PATCH v6 3/9] clk: mediatek: Add __initdata and __init for data and functions James Liao
2015-08-04 8:16 ` [PATCH v6 4/9] clk: mediatek: Add fixed clocks support for Mediatek SoC James Liao
2015-08-04 8:16 ` [PATCH v6 5/9] clk: mediatek: Fix rate and dependency of MT8173 clocks James Liao
2015-08-05 6:53 ` Sascha Hauer
2015-08-06 8:35 ` James Liao
2015-08-06 8:59 ` Sascha Hauer
2015-08-04 8:16 ` [PATCH v6 6/9] dt-bindings: ARM: Mediatek: Document devicetree bindings for clock controllers James Liao
2015-08-04 8:16 ` [PATCH v6 7/9] clk: mediatek: Add subsystem clocks of MT8173 James Liao
2015-08-05 6:46 ` Sascha Hauer
2015-08-05 7:26 ` Daniel Kurtz
2015-08-05 7:36 ` Sascha Hauer
2015-08-05 7:41 ` Daniel Kurtz
2015-08-05 7:50 ` Sascha Hauer
2015-08-05 7:58 ` Daniel Kurtz
2015-08-06 8:23 ` James Liao [this message]
2015-08-06 8:53 ` Sascha Hauer
2015-08-06 9:00 ` James Liao
2015-08-06 9:13 ` Daniel Kurtz
2015-08-06 10:20 ` Sascha Hauer
2015-08-07 2:20 ` James Liao
2015-08-07 8:05 ` Daniel Kurtz
2015-08-07 8:06 ` Daniel Kurtz
2015-08-04 8:16 ` [PATCH v6 8/9] clk: mediatek: Add USB clock support in MT8173 APMIXEDSYS James Liao
2015-08-04 8:16 ` [PATCH v6 9/9] arm64: dts: mt8173: Add subsystem clock controller device nodes James Liao
2015-08-04 13:46 ` [PATCH v6 0/9] Fixes and new clocks support for Mediatek MT8173 Daniel Kurtz
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=1438849431.27884.9.camel@mtksdaap41 \
--to=jamesjj.liao@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.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