From: Peter De Schrijver <pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v3 4/4] soc/tegra: pmc: apply MBIST work around fo Tegra210
Date: Thu, 25 Jan 2018 14:26:13 +0200 [thread overview]
Message-ID: <20180125122613.GM7031@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <fe422430-cb85-c28d-404b-98e7b87c15e0-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On Thu, Jan 25, 2018 at 10:57:36AM +0000, Jon Hunter wrote:
>
> On 25/01/18 10:06, Peter De Schrijver wrote:
> > On Wed, Jan 24, 2018 at 10:43:45PM +0000, Jon Hunter wrote:
> >>
> >> On 23/01/18 09:22, Peter De Schrijver wrote:
> >>> Apply the memory built-in self test work around when ungating certain
> >>> Tegra210 power domains.
> >>
> >> Nit-pick .. typo in $subject.
> >>
> >>> Signed-off-by: Peter De Schrijver <pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> >>> ---
> >>> drivers/soc/tegra/pmc.c | 5 +++++
> >>> 1 file changed, 5 insertions(+)
> >>>
> >>> diff --git a/drivers/soc/tegra/pmc.c b/drivers/soc/tegra/pmc.c
> >>> index ce62a47..c4eff4b 100644
> >>> --- a/drivers/soc/tegra/pmc.c
> >>> +++ b/drivers/soc/tegra/pmc.c
> >>> @@ -153,6 +153,7 @@ struct tegra_pmc_soc {
> >>>
> >>> bool has_tsense_reset;
> >>> bool has_gpu_clamps;
> >>> + bool needs_mbist_war;
> >>>
> >>> const struct tegra_io_pad_soc *io_pads;
> >>> unsigned int num_io_pads;
> >>> @@ -431,6 +432,9 @@ static int tegra_powergate_power_up(struct tegra_powergate *pg,
> >>>
> >>> usleep_range(10, 20);
> >>>
> >>> + if (pg->pmc->soc->needs_mbist_war)
> >>> + tegra210_clk_handle_mbist_war(pg->id);
> >>> +
> >>
> >> Be good if we could return an error from the above function.
> >>
> >
> > We need to also undo whatever we did before then.
>
> I think it is fine if on error you 'goto disable_clks'.
Shouldn't we do this for tegra_powergate_reset_deassert() failure as well then?
Also in case of tegra_powergate_enable_clocks() failure we should probably jump
to powergate_off because tegra_powergate_enable_clocks() will disable the
already enabled clocks on failure.
Peter.
next prev parent reply other threads:[~2018-01-25 12:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 9:22 [PATCH v3 0/4] MBIST work around (WAR) for Tegra210 Peter De Schrijver
2018-01-23 9:22 ` [PATCH v3 1/4] clk: tegra: Add la clock " Peter De Schrijver
[not found] ` <1516699369-3513-2-git-send-email-pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-01-24 10:03 ` Jon Hunter
[not found] ` <31118e4b-80bd-1db2-0a82-9359b99deccf-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-01-24 11:23 ` Peter De Schrijver
2018-01-23 9:22 ` [PATCH v3 2/4] clk: tegra: add fence_delay for clock registers Peter De Schrijver
2018-01-24 10:20 ` Jon Hunter
2018-01-23 9:22 ` [PATCH v3 3/4] clk: tegra: MBIST work around for Tegra210 Peter De Schrijver
2018-01-24 21:59 ` Jon Hunter
[not found] ` <637b3bb4-1ac0-5612-ec2e-5740e611b11a-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-01-25 9:02 ` Peter De Schrijver
[not found] ` <20180125090255.GK7031-Rysk9IDjsxmJz7etNGeUX8VPkgjIgRvpAL8bYrjMMd8@public.gmane.org>
2018-01-25 10:19 ` Jon Hunter
[not found] ` <a161a11c-1794-ebc4-3ff0-7624c23cabdb-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-01-25 12:41 ` Peter De Schrijver
[not found] ` <20180125124157.GN7031-Rysk9IDjsxmJz7etNGeUX8VPkgjIgRvpAL8bYrjMMd8@public.gmane.org>
2018-01-25 13:04 ` Jon Hunter
2018-01-23 9:22 ` [PATCH v3 4/4] soc/tegra: pmc: apply MBIST work around fo Tegra210 Peter De Schrijver
2018-01-24 22:43 ` Jon Hunter
[not found] ` <cf919367-4521-25b1-1f80-16e2b660045e-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-01-25 10:06 ` Peter De Schrijver
2018-01-25 10:57 ` Jon Hunter
[not found] ` <fe422430-cb85-c28d-404b-98e7b87c15e0-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-01-25 12:26 ` Peter De Schrijver [this message]
[not found] ` <20180125122613.GM7031-Rysk9IDjsxmJz7etNGeUX8VPkgjIgRvpAL8bYrjMMd8@public.gmane.org>
2018-01-25 13:07 ` 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=20180125122613.GM7031@tbergstrom-lnx.Nvidia.com \
--to=pdeschrijver-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=jonathanh-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox