From: Stephen Boyd <sboyd@kernel.org>
To: Dmitry Osipenko <digetx@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Joseph Lo <josephl@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-clk@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/5] clk: tegra: emc: Support multiple RAM codes
Date: Thu, 25 Apr 2019 13:54:59 -0700 [thread overview]
Message-ID: <155622569977.15276.16514341758951287015@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20190414192321.23294-3-digetx@gmail.com>
Quoting Dmitry Osipenko (2019-04-14 12:23:18)
> The timings parser doesn't append timings, but instead it parses only
> the first timing and hence doesn't store all of the timings when
> device-tree has timings for multiple RAM codes. In a result EMC scaling
> doesn't work if timings are missing.
>
> Tested-by: Steev Klimaszewski <steev@kali.org>
> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> ---
Applied to clk-next
next prev parent reply other threads:[~2019-04-25 20:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 19:23 [PATCH v2 0/5] clk: tegra: EMC/MC clock fixes and improvements Dmitry Osipenko
2019-04-14 19:23 ` [PATCH v2 1/5] clk: tegra: emc: Don't enable EMC clock manually Dmitry Osipenko
2019-04-25 20:54 ` Stephen Boyd
2019-04-14 19:23 ` [PATCH v2 2/5] clk: tegra: emc: Support multiple RAM codes Dmitry Osipenko
2019-04-25 20:54 ` Stephen Boyd [this message]
2019-04-14 19:23 ` [PATCH v2 3/5] clk: tegra: emc: Fix EMC max-rate clamping Dmitry Osipenko
2019-04-25 20:55 ` Stephen Boyd
2019-04-14 19:23 ` [PATCH v2 4/5] clk: tegra: emc: Replace BUG() with WARN_ONCE() Dmitry Osipenko
2019-04-25 20:55 ` Stephen Boyd
2019-04-14 19:23 ` [PATCH v2 5/5] clk: tegra: divider: Mark Memory Controller clock as read-only Dmitry Osipenko
2019-04-25 20:55 ` 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=155622569977.15276.16514341758951287015@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=josephl@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=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).