From: Dmitry Osipenko <digetx@gmail.com>
To: Stephen Boyd <sboyd@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Michael Turquette <mturquette@baylibre.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] clk: tegra30: Use 300MHz for video decoder by default
Date: Sun, 15 Nov 2020 17:10:04 +0300 [thread overview]
Message-ID: <b362195a-665d-5e1d-4c6e-26cbc2459777@gmail.com> (raw)
In-Reply-To: <160538861846.60232.2236874455363048014@swboyd.mtv.corp.google.com>
15.11.2020 00:16, Stephen Boyd пишет:
> Quoting Dmitry Osipenko (2020-11-04 05:48:10)
>> The 600MHz is a too high clock rate for some SoC versions for the video
>> decoder hardware and this may cause stability issues. Use 300MHz for the
>> video decoder by default, which is supported by all hardware versions.
>>
>> Fixes: ed1a2459e20c ("clk: tegra: Add Tegra20/30 EMC clock implementation")
>> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
>> ---
>
> Should this go to clk-fixes? Thierry?
>
Either way should be good. The fix isn't critical because 600MHz seems
to be working okay on unsupported hardware.
Potentially this could vary depending on a board, but then I don't think
that there are actively-supported boards which would notice this change.
Likely that this patch will be backported by a bot anyways because of
the fixes tag.
next prev parent reply other threads:[~2020-11-15 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 13:48 Dmitry Osipenko
2020-11-14 21:16 ` Stephen Boyd
2020-11-15 14:10 ` Dmitry Osipenko [this message]
2020-11-25 2:15 ` 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=b362195a-665d-5e1d-4c6e-26cbc2459777@gmail.com \
--to=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@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
all inboxes | Powered by JetHome®