Thread (14 messages) 14 messages, 3 authors, 2013-06-03
DORMANTno replies
Revisions (9)
  1. v1 [diff vs current]
  2. v1 [diff vs current]
  3. v1 [diff vs current]
  4. v1 [diff vs current]
  5. v2 [diff vs current]
  6. v2 [diff vs current]
  7. v2 [diff vs current]
  8. v2 [diff vs current]
  9. v2 current

[PATCH V2 3/6] ARM: tegra: make tegra_resume can work for Tegra114

From: Joseph Lo <hidden>
Date: 2013-06-03 02:16:06
Also in: linux-tegra

On Sat, 2013-06-01 at 17:47 +0800, Arnd Bergmann wrote:
On Saturday 01 June 2013, Stephen Warren wrote:
quoted
On 05/31/2013 04:41 PM, Arnd Bergmann wrote:
quoted
On Monday 20 May 2013, Joseph Lo wrote:
quoted
+       cpu_to_csr_req r1, r0
+       mov32   r2, TEGRA_FLOW_CTRL_BASE
+       ldr     r1, [r2, r1]
This causes build errors now, since cpu_to_csr_req is not defined anywhere.
What build error are you seeing? I built next-20130531 earlier today
without any issue.

I do remember making a similar comment during review of this patch that
cpu_to_csr_req wasn't defined anywhere, but IIRC Joseph pointed me to
another patch in the series which had added it, or something like that.
Sorry, I should have mentioned it was using randconfig, all the defconfig
builds work fine. The code is inside of "#ifndef CONFIG_ARCH_TEGRA_2x_SOC",
but Tegra2 is normally enabled in defconfig, so it does not get built.

I suspect the #ifdef is wrong as well, and should have been "if tegra3
or tegra4" instead. Joseph, can you clarify the intent of this?

	Arnd
Arnd,

I think the "ifdef" should be removed here because we had a runtime
Tegra SoC detection code here, the "ifdef" here would cause the code
won't be built for the tegra_defconfig that we are using. And a typo
need to fix here, it should be "cpu_to_csr_reg" not "cpu_to_csr_req".
Sorry.

Thanks for report. Will provide a fix.

Joseph
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help