From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] clk: tegra: Make vde a child of pll_c3
Date: Mon, 11 Jun 2018 17:17:31 +0300 [thread overview]
Message-ID: <5479310.ZEnOGiWBp7@dimapc> (raw)
In-Reply-To: <20180611082037.31796-1-thierry.reding@gmail.com>
On Monday, 11 June 2018 11:20:37 MSK Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The current default is to leave the VDE clock's parent at the default,
> which is clk_m. However, that is not a configuration that will allow the
> VDE to function. Reparent it to pll_c3 instead to make sure the hardware
> can actually decode video content.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> drivers/clk/tegra/clk-tegra124.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clk/tegra/clk-tegra124.c
> b/drivers/clk/tegra/clk-tegra124.c index f5048f82c0b9..b6cf28ca2ed2 100644
> --- a/drivers/clk/tegra/clk-tegra124.c
> +++ b/drivers/clk/tegra/clk-tegra124.c
> @@ -1267,7 +1267,7 @@ static struct tegra_clk_init_table common_init_table[]
> __initdata = { { TEGRA124_CLK_I2S2, TEGRA124_CLK_PLL_A_OUT0, 11289600, 0 },
> { TEGRA124_CLK_I2S3, TEGRA124_CLK_PLL_A_OUT0, 11289600, 0 },
> { TEGRA124_CLK_I2S4, TEGRA124_CLK_PLL_A_OUT0, 11289600, 0 },
> - { TEGRA124_CLK_VDE, TEGRA124_CLK_CLK_MAX, 600000000, 0 },
> + { TEGRA124_CLK_VDE, TEGRA124_CLK_PLL_C3, 600000000, 0 },
> { TEGRA124_CLK_HOST1X, TEGRA124_CLK_PLL_P, 136000000, 1 },
> { TEGRA124_CLK_DSIALP, TEGRA124_CLK_PLL_P, 68000000, 0 },
> { TEGRA124_CLK_DSIBLP, TEGRA124_CLK_PLL_P, 68000000, 0 },
If clk_m isn't a valid configuration, why VDE could select it? At least TRM
lists clk_m as a valid source and clk_m is running on a safe 120 MHz, VDE HW
should work fine. Sounds like a clock driver bug to me.
Seems VDE clock on should be ~366 MHz according to the T40/T124 TRM. See
"5.3.8 PLLC, PLLC2, PLLC3, and PLLC4" of the T124 TRM.
Would be nice if you could adjust the VDE clock rate / parent-clock on all
Tegra's, i.e. explicitly set the parent clock and the rate to 300-400 MHz.
next prev parent reply other threads:[~2018-06-11 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 8:20 [PATCH] clk: tegra: Make vde a child of pll_c3 Thierry Reding
2018-06-11 14:17 ` Dmitry Osipenko [this message]
2018-06-11 16:05 ` Thierry Reding
2018-06-11 16:45 ` Dmitry Osipenko
2018-06-12 15:43 ` Peter De Schrijver
2018-07-09 0:06 ` 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=5479310.ZEnOGiWBp7@dimapc \
--to=digetx@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=sboyd@kernel.org \
--cc=thierry.reding@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).