From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/4] ARM: HYP/non-sec: Make armv7_init_nonsec() usable before relocation
Date: Mon, 27 Oct 2014 10:41:41 +0100 [thread overview]
Message-ID: <20141027104141.1d02374c@lilith> (raw)
In-Reply-To: <4adda4d321cc4de6859477b23d3b2578@DM2PR03MB574.namprd03.prod.outlook.com>
Hello Yuantian,
On Thu, 16 Oct 2014 04:42:06 +0000, Yuantian Tang
<Yuantian.Tang@freescale.com> wrote:
> > >> Wouldn't it be better to declare gic_dist_base as a local variable?
> > >>It is only used once outside function armv7_switch_nonsec(). It could
> > >>be replaced with
> > >> get_gicd_base_address() call.
> > >>
> > >I am with you. That's what I did in the first version of this patch.
> > >Patch links is at: http://patchwork.ozlabs.org/patch/391065/
> > >But Albert seems have some concerns. The attached is what we discussed.
FTR, I only had concerns with the patch subject / commit summary.
Regarding the patch itself, I just asked whether the global was not
used as some means of coordination which would have been broken by
turning it into a local, but you had checked, so that was fine.
> > >Now on the second thought, I prefer the way this patch proposed because
> > >if we define gic_dist_base as local variable, That means function
> > >get_gicd_base_address() should be usable at any time in any mode. Can
> > >we make sure of that in the future?
> >
> > I don't strongly object introducing a new local variable. But I don't see how the
> > global variable is useful. Function get_gicd_base_address() should be available all
> > the time. It reads PERIPHBASE register, or return a macro. It hasn't changed
> > since the first patch added it in 2013. Not sure if the original author Andre
> > Przywara is available to comments.
> >
> Thanks for your comments.
> If no one objects the original patch, I like to resubmit it.
>
> Hi Albert, what's your opinion on this?
Which 'original patch' do you mean?
If it is http://patchwork.ozlabs.org/patch/391065/ then I'm fine with
it and will apply it.
> Regards,
> Yuantian
>
> > York
> >
Amicalement,
--
Albert.
next prev parent reply other threads:[~2014-10-27 9:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 8:11 [U-Boot] [PATCH 0/4] Deep sleep patches for Freescale QorIQ platforms Yuantian.Tang at freescale.com
2014-10-09 8:11 ` [U-Boot] [PATCH 1/4] Add deep sleep framework support " Yuantian.Tang at freescale.com
2014-10-09 8:11 ` [U-Boot] [PATCH 2/4] ARM: HYP/non-sec: Make armv7_init_nonsec() usable before relocation Yuantian.Tang at freescale.com
2014-10-15 15:44 ` York Sun
2014-10-16 3:02 ` Yuantian Tang
2014-10-16 3:36 ` York Sun
2014-10-16 4:42 ` Yuantian Tang
2014-10-27 9:41 ` Albert ARIBAUD [this message]
2014-10-28 2:24 ` Yuantian Tang
2014-10-28 6:48 ` Albert ARIBAUD
2014-10-09 8:11 ` [U-Boot] [PATCH 3/4] arm: ls102xa: Fixed a register definition error Yuantian.Tang at freescale.com
2014-11-25 17:51 ` York Sun
2014-10-09 8:11 ` [U-Boot] [PATCH 4/4] arm: ls1021qds: Add deep sleep support Yuantian.Tang at freescale.com
2014-10-13 9:41 ` [U-Boot] [PATCH 0/4] Deep sleep patches for Freescale QorIQ platforms Yuantian Tang
2014-10-13 9:46 ` Albert ARIBAUD
2014-10-14 2:30 ` Yuantian Tang
-- strict thread matches above, loose matches on Subject: below --
2014-09-28 8:59 Yuantian.Tang at freescale.com
2014-09-28 8:59 ` [U-Boot] [PATCH 2/4] ARM: HYP/non-sec: Make armv7_init_nonsec() usable before relocation Yuantian.Tang at freescale.com
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=20141027104141.1d02374c@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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