From: Andre Heider <a.heider@gmail.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: jonathanh@nvidia.com, linux-clk@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v4 0/4] MBIST work around (WAR) for Tegra210
Date: Tue, 13 Feb 2018 06:54:48 +0100 [thread overview]
Message-ID: <4de03c4d-c5c1-f3ea-1ddc-cd5990aadb47@gmail.com> (raw)
In-Reply-To: <1516888813-32180-1-git-send-email-pdeschrijver@nvidia.com>
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.
For the series:
Tested-by: Andre Heider <a.heider@gmail.com>
With one patch on top [0] this finally fixes the 'green bars' issue, see
[1].
Thanks!
Andre
[0]
https://github.com/thierryreding/linux/commit/13eea63a70de753466fc644f55a134a13b9b584b
[1] https://github.com/denysvitali/linux-on-pixel-c/issues/1
prev parent reply other threads:[~2018-02-13 5:54 UTC|newest]
Thread overview: 12+ 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
[not found] ` <1516888813-32180-1-git-send-email-pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-01-25 14:00 ` [PATCH v4 1/4] clk: tegra: Add la clock " Peter De Schrijver
2018-01-25 14:00 ` [PATCH v4 3/4] clk: tegra: MBIST work around " Peter De Schrijver
2018-01-26 9:37 ` [PATCH v4 0/4] MBIST work around (WAR) " Jon Hunter
2018-02-12 16:17 ` Hector Martin 'marcan'
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 4/4] soc/tegra: pmc: MBIST work around for Tegra210 Peter De Schrijver
2018-02-12 12:05 ` [PATCH v4 0/4] MBIST work around (WAR) " Mikko Perttunen
[not found] ` <a40f0593-24d8-a91e-9f8c-f7eafc379591-/1wQRMveznE@public.gmane.org>
2018-02-12 12:34 ` Peter De Schrijver
2018-02-13 9:32 ` Mikko Perttunen
2018-02-12 16:09 ` Thierry Reding
2018-02-13 5:54 ` Andre Heider [this message]
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=4de03c4d-c5c1-f3ea-1ddc-cd5990aadb47@gmail.com \
--to=a.heider@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pdeschrijver@nvidia.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