All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter De Schrijver <pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Peter De Schrijver
	<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: [PATCH v2 0/4] MBIST work around (WAR) for Tegra210
Date: Thu, 16 Nov 2017 17:29:51 +0200	[thread overview]
Message-ID: <1510846195-28555-1-git-send-email-pdeschrijver@nvidia.com> (raw)

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 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: apply MBIST work around fo Tegra210

 drivers/clk/tegra/clk-tegra210.c         | 371 ++++++++++++++++++++++++++++++-
 drivers/clk/tegra/clk.h                  |   7 +
 drivers/soc/tegra/pmc.c                  |   5 +
 include/dt-bindings/clock/tegra210-car.h |   2 +-
 include/linux/clk/tegra.h                |   1 +
 5 files changed, 383 insertions(+), 3 deletions(-)

-- 
1.9.1

WARNING: multiple messages have this Message-ID (diff)
From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: <linux-tegra@vger.kernel.org>, <linux-clk@vger.kernel.org>
Cc: Peter De Schrijver <pdeschrijver@nvidia.com>
Subject: [PATCH v2 0/4] MBIST work around (WAR) for Tegra210
Date: Thu, 16 Nov 2017 17:29:51 +0200	[thread overview]
Message-ID: <1510846195-28555-1-git-send-email-pdeschrijver@nvidia.com> (raw)

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 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: apply MBIST work around fo Tegra210

 drivers/clk/tegra/clk-tegra210.c         | 371 ++++++++++++++++++++++++++++++-
 drivers/clk/tegra/clk.h                  |   7 +
 drivers/soc/tegra/pmc.c                  |   5 +
 include/dt-bindings/clock/tegra210-car.h |   2 +-
 include/linux/clk/tegra.h                |   1 +
 5 files changed, 383 insertions(+), 3 deletions(-)

-- 
1.9.1


             reply	other threads:[~2017-11-16 15:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 15:29 Peter De Schrijver [this message]
2017-11-16 15:29 ` [PATCH v2 0/4] MBIST work around (WAR) for Tegra210 Peter De Schrijver
     [not found] ` <1510846195-28555-1-git-send-email-pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-11-16 15:29   ` [PATCH v2 1/4] clk: tegra: Add la clock " Peter De Schrijver
2017-11-16 15:29     ` Peter De Schrijver
2017-11-16 15:29   ` [PATCH v2 2/4] clk: tegra: add fence_delay for clock registers Peter De Schrijver
2017-11-16 15:29     ` Peter De Schrijver
2017-11-16 15:29   ` [PATCH v2 3/4] clk: tegra: MBIST work around for Tegra210 Peter De Schrijver
2017-11-16 15:29     ` Peter De Schrijver
2017-11-16 15:29   ` [PATCH v2 4/4] soc/tegra: pmc: apply MBIST work around fo Tegra210 Peter De Schrijver
2017-11-16 15:29     ` Peter De Schrijver
2017-11-16 15:32   ` [PATCH v2 0/4] MBIST work around (WAR) for Tegra210 Peter De Schrijver
2017-11-16 15:32     ` Peter De Schrijver
  -- strict thread matches above, loose matches on Subject: below --
2017-11-16 14:28 Peter De Schrijver
2017-11-16 14:28 ` Peter De Schrijver
     [not found] ` <1510842542-16451-1-git-send-email-pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-12-19  8:53   ` Peter De Schrijver
2017-12-19  8:53     ` Peter De Schrijver
     [not found]     ` <20171219085346.GK29417-Rysk9IDjsxmJz7etNGeUX8VPkgjIgRvpAL8bYrjMMd8@public.gmane.org>
2017-12-19  9:40       ` Jon Hunter
2017-12-19  9:40         ` Jon Hunter
2017-12-20 10:12   ` Jon Hunter
2017-12-20 10:12     ` Jon Hunter
     [not found]     ` <83325ffd-5b85-6288-63ac-5a938b948300-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-12-21  9:37       ` Peter De Schrijver
2017-12-21  9:37         ` Peter De Schrijver
     [not found]         ` <20171221093742.GW29417-Rysk9IDjsxmJz7etNGeUX8VPkgjIgRvpAL8bYrjMMd8@public.gmane.org>
2017-12-21 11:11           ` Jon Hunter
2017-12-21 11:11             ` Jon Hunter

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=1510846195-28555-1-git-send-email-pdeschrijver@nvidia.com \
    --to=pdeschrijver-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
    --cc=linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.