From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] soc/tegra: Register SoC device
Date: Tue, 22 Aug 2017 16:00:58 +0100 [thread overview]
Message-ID: <cdca760a-0292-c70c-c4cf-99983ee37e6e@arm.com> (raw)
In-Reply-To: <20170822111922.GA15965@ulmo>
On 22/08/17 12:19, Thierry Reding wrote:
> On Tue, Aug 22, 2017 at 11:15:21AM +0100, Sudeep Holla wrote:
>>
>>
>> On 17/08/17 15:42, Thierry Reding wrote:
>>> From: Thierry Reding <treding@nvidia.com>
>>>
>>> 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
next prev parent reply other threads:[~2017-08-22 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 14:42 [PATCH] soc/tegra: Register SoC device Thierry Reding
2017-08-22 10:15 ` Sudeep Holla
2017-08-22 11:19 ` Thierry Reding
2017-08-22 15:00 ` Sudeep Holla [this message]
2017-08-23 8:49 ` Arnd Bergmann
2017-08-23 9:11 ` Thierry Reding
2017-08-23 9:21 ` Arnd Bergmann
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=cdca760a-0292-c70c-c4cf-99983ee37e6e@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.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