From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Joseph Lo <josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] ARM: tegra: remove the ifdef of ARCH SoC in the tegra_resume
Date: Mon, 03 Jun 2013 09:26:21 -0600 [thread overview]
Message-ID: <51ACB59D.9030005@wwwdotorg.org> (raw)
In-Reply-To: <1370247004-31846-1-git-send-email-josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 06/03/2013 02:10 AM, Joseph Lo wrote:
> Removing the ifdef of ARCH_TEGRA_SoC in the tegra_resume function. Because
> we always build with all Tegra SoCs support and had a runtime chip
> detection code there. And we expect most of the chips would need the code
> in the future.
>
> We also fix a typo of a macro name that cause a build error.
OK, this fixes the build issue, but this patch raises some questions
about the code...
> diff --git a/arch/arm/mach-tegra/reset-handler.S b/arch/arm/mach-tegra/reset-handler.S
> -#ifndef CONFIG_ARCH_TEGRA_2x_SOC
> /* Are we on Tegra20? */
> cmp r6, #TEGRA20
> beq 1f @ Yes
Was that ifdef completely incorrect before? I can see why the cmp/beq
might be ifdef'd (although it's not worth it), but I assume the code
after that beq was intended to run on all chips after Tegra20. The ifdef
as it was written does something rather different; it prevents any of
that code from running unless the kernel doesn't have Tegra20 support.
So, I think that the removal of the ifdef is more of a bug-fix that
"because we always build with all Tegra SoCs support. Let me know, and
I'll re-write the commit description to something more accurate...
> /* Clear the flow controller flags for this CPU. */
> - cpu_to_csr_req r1, r0
> + cpu_to_csr_reg r1, r0
> mov32 r2, TEGRA_FLOW_CTRL_BASE
> ldr r1, [r2, r1]
> /* Clear event & intr flag */
> @@ -70,7 +69,6 @@ no_cpu0_chk:
> bic r1, r1, r0
> str r1, [r2]
> 1:
> -#endif
>
> check_cpu_part_num 0xc09, r8, r9
> bne not_ca9
next prev parent reply other threads:[~2013-06-03 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 8:10 [PATCH] ARM: tegra: remove the ifdef of ARCH SoC in the tegra_resume Joseph Lo
[not found] ` <1370247004-31846-1-git-send-email-josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-06-03 15:26 ` Stephen Warren [this message]
2013-06-03 22:48 ` Arnd Bergmann
[not found] ` <201306040048.13612.arnd-r2nGTMty4D4@public.gmane.org>
2013-06-04 1:25 ` Joseph Lo
2013-06-05 17:44 ` Stephen Warren
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=51ACB59D.9030005@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@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