From: Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Peter De Schrijver
<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/4] clk: tegra: Add la clock for Tegra210
Date: Tue, 14 Nov 2017 16:42:56 -0800 [thread overview]
Message-ID: <20171115004256.GN11955@codeaurora.org> (raw)
In-Reply-To: <1510313868-24810-2-git-send-email-pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 11/10, Peter De Schrijver wrote:
> This clock is needed by the MBIST WAR.
I'm not sure everyone knows what WAR means. Maybe it can be
spelled out as "workaround". Same comment applies to MBIST.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-11-15 0:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 11:37 [PATCH 0/4] MBIST WAR for Tegra210 Peter De Schrijver
[not found] ` <1510313868-24810-1-git-send-email-pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-11-10 11:37 ` [PATCH 1/4] clk: tegra: Add la clock " Peter De Schrijver
[not found] ` <1510313868-24810-2-git-send-email-pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-11-15 0:42 ` Stephen Boyd [this message]
2017-11-10 11:37 ` [PATCH 2/4] clk: tegra: add fence_delay for clock registers Peter De Schrijver
[not found] ` <1510313868-24810-3-git-send-email-pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-11-15 0:41 ` Stephen Boyd
[not found] ` <20171115004132.GM11955-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-11-16 11:27 ` Peter De Schrijver
2017-11-10 11:37 ` [PATCH 3/4] clk: tegra: MBIST WAR for Tegra210 Peter De Schrijver
2017-11-10 11:37 ` [PATCH 4/4] soc/tegra: pmc: apply " Peter De Schrijver
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=20171115004256.GN11955@codeaurora.org \
--to=sboyd-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
--cc=linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@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 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).