Thread (7 messages) 7 messages, 3 authors, 2017-08-23
STALE3222d

[PATCH] soc/tegra: Register SoC device

From: Sudeep Holla <hidden>
Date: 2017-08-22 15:00:58
Also in: linux-tegra


On 22/08/17 12:19, Thierry Reding wrote:
On Tue, Aug 22, 2017 at 11:15:21AM +0100, Sudeep Holla wrote:
quoted

On 17/08/17 15:42, Thierry Reding wrote:
quoted
From: Thierry Reding <redacted>

Move this code from arch/arm/mach-tegra and make it common among 32-bit
and 64-bit Tegra SoCs. This is slightly complicated by the fact that on
32-bit Tegra, the SoC device is used as the parent for all devices that
are instantiated from device tree.
This seem to be in linux-next and causing the below splat on my platform
which is not Tegra :)

WARNING: .... at drivers/soc/tegra/fuse/tegra-apbmisc.c:48
tegra_get_chip_id+0x30/0x40
Modules linked in:
CPU: 2 PID: 1 Comm: swapper/0 Not tainted
4.13.0-rc6-next-20170822-00008-g52a8e57512ae #13
task: ffff8009768a0000 task.stack: ffff000008038000
PC is at tegra_get_chip_id+0x30/0x40
LR is at tegra_get_chip_id+0x30/0x40
 tegra_get_chip_id+0x30/0x40
 tegra_soc_device_register+0x68/0xd0
 tegra_init_soc+0x10/0x44
 do_one_initcall+0x38/0x120
 kernel_init_freeable+0x184/0x224
 kernel_init+0x10/0x100
 ret_from_fork+0x10/0x18
Indeed. Does the below patch fix this?
Yes, it does.

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