From: Thierry Reding <thierry.reding@gmail.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: Peter De Schrijver <pdeschrijver@nvidia.com>,
jonathanh@nvidia.com, linux-tegra@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH v4 0/4] MBIST work around (WAR) for Tegra210
Date: Mon, 12 Feb 2018 17:09:03 +0100 [thread overview]
Message-ID: <20180212160903.GA4287@ulmo> (raw)
In-Reply-To: <1516888813-32180-1-git-send-email-pdeschrijver@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1888 bytes --]
On Thu, Jan 25, 2018 at 04:00:09PM +0200, Peter De Schrijver wrote:
> This patch series introduces the Memory Built-In Self Test (MBIST)
> work around (WAR) needed when power ungating certain domains. More
> details can be found in 'clk: tegra: MBIST WAR for Tegra210'. I choose to
> implement the WAR in the Tegra210 clock driver, because most accesses are
> to CAR registers and for the VENC domain, we need to make sure the CSI
> clock source is not changed during the WAR execution.
>
> Changes in v4:
> * moved locking and clock control to tegra210_clk_handle_mbist_war()
> * propagate errors during WAR execution to user
> * rework error handling tegra210_mbist_clk_init() slightly
>
> Changes in v3:
> * fix compile problem on non-Tegra210 platforms
> * fix clock handling bug in tegra210_generic_mbist_war()
> * addressed minor comments
>
> Changes in v2:
> * Use readl for fence_delay() rather than readl_relaxed
> * clarify MBIST and WAR acronyms
>
> Peter De Schrijver (4):
> clk: tegra: Add la clock for Tegra210
> clk: tegra: add fence_delay for clock registers
> clk: tegra: MBIST work around for Tegra210
> soc/tegra: pmc: MBIST work around for Tegra210
>
> drivers/clk/tegra/clk-tegra210.c | 357 ++++++++++++++++++++++++++++++-
> drivers/clk/tegra/clk.h | 7 +
> drivers/soc/tegra/pmc.c | 7 +
> include/dt-bindings/clock/tegra210-car.h | 2 +-
> include/linux/clk/tegra.h | 6 +
> 5 files changed, 376 insertions(+), 3 deletions(-)
Hi Mike, Stephen,
since there's a dependency from patch 4 to patch 3 in the series, do you
mind if I take this in via the Tegra tree? I can send out a pull request
for the clock branch sometime later in the release cycle and pick up any
other Tegra clock related patches that may show up in the meantime.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-12 16:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 14:00 [PATCH v4 0/4] MBIST work around (WAR) for Tegra210 Peter De Schrijver
2018-01-25 14:00 ` [PATCH v4 1/4] clk: tegra: Add la clock " Peter De Schrijver
2018-01-25 14:00 ` [PATCH v4 2/4] clk: tegra: add fence_delay for clock registers Peter De Schrijver
2018-01-25 14:00 ` [PATCH v4 3/4] clk: tegra: MBIST work around for Tegra210 Peter De Schrijver
2018-01-25 14:00 ` [PATCH v4 4/4] soc/tegra: pmc: " Peter De Schrijver
2018-01-26 9:37 ` [PATCH v4 0/4] MBIST work around (WAR) " Jon Hunter
2018-02-12 12:05 ` Mikko Perttunen
2018-02-12 12:34 ` Peter De Schrijver
2018-02-13 9:32 ` Mikko Perttunen
2018-02-12 16:09 ` Thierry Reding [this message]
2018-03-09 18:25 ` Stephen Boyd
2018-02-12 16:17 ` Hector Martin 'marcan'
2018-02-13 5:54 ` Andre Heider
2018-03-08 14:36 ` Thierry Reding
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=20180212160903.GA4287@ulmo \
--to=thierry.reding@gmail.com \
--cc=jonathanh@nvidia.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 \
/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).