From: Guenter Roeck <linux@roeck-us.net>
To: Michael Tretter <m.tretter@pengutronix.de>
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
michal.simek@xilinx.com, devicetree@vger.kernel.org,
Rajan Vaja <rajanv@xilinx.com>,
Rajan Vaja <rajan.vaja@xilinx.com>,
linux-arm-kernel@lists.infradead.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/5] arm64: zynqmp: Add firmware DT node
Date: Sun, 8 Dec 2019 14:38:14 -0800 [thread overview]
Message-ID: <20191208223814.GA21260@roeck-us.net> (raw)
In-Reply-To: <20191018160735.15658-2-m.tretter@pengutronix.de>
On Fri, Oct 18, 2019 at 06:07:31PM +0200, Michael Tretter wrote:
> From: Rajan Vaja <rajan.vaja@xilinx.com>
>
> Add firmware DT node in ZynqMP device tree. This node
> uses bindings as per new firmware interface driver.
>
> Signed-off-by: Rajan Vaja <rajanv@xilinx.com>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
With this patch applied in the mainline kernel, the qemu xlnx-zcu102
emulation crashes (see below). Any idea what it might take to get
qemu back to working ?
Thanks,
Guenter
---
[ 30.719268] ------------[ cut here ]------------
[ 30.719403] kernel BUG at arch/arm64/kernel/traps.c:406!
[ 30.719971] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
[ 30.720358] Modules linked in:
[ 30.720741] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.4.0-13331-g9455d25f4e3b #1
[ 30.720852] Hardware name: ZynqMP ZCU102 Rev1.0 (DT)
[ 30.721157] pstate: 00000005 (nzcv daif -PAN -UAO)
[ 30.721261] pc : do_undefinstr+0x2f4/0x318
[ 30.721336] lr : do_undefinstr+0x1fc/0x318
[ 30.721410] sp : ffff80001003b930
[ 30.721486] x29: ffff80001003b930 x28: ffff00007d178040
[ 30.721597] x27: 0000000000000000 x26: ffff8000117d0514
[ 30.721683] x25: ffff8000118c90d0 x24: 0000000000000000
[ 30.721769] x23: 0000000040000005 x22: 00000000d4000003
[ 30.721854] x21: ffff800011e1c850 x20: ffff80001003b990
[ 30.721940] x19: ffff800011e0fa08 x18: 0000000000000001
[ 30.722025] x17: ffff800010c0f1d8 x16: ffff800010c11fb8
[ 30.722111] x15: ffffffffffffffff x14: ffffffffffffffff
[ 30.722196] x13: 0000000000000018 x12: 0101010101010101
[ 30.722281] x11: 0000000000000000 x10: 00000000628e21fa
[ 30.722384] x9 : ffff00007d178858 x8 : ffff00007d178880
[ 30.722471] x7 : ffff80001003b8b0 x6 : 0000000000000001
[ 30.722560] x5 : 0000000000000001 x4 : 0000000000000001
[ 30.722646] x3 : 0000000000000000 x2 : 00000000000174b1
[ 30.722730] x1 : ffff00007d178040 x0 : 0000000040000005
[ 30.722913] Call trace:
[ 30.722993] do_undefinstr+0x2f4/0x318
[ 30.723070] el1_sync_handler+0xb0/0x108
[ 30.723138] el1_sync+0x7c/0x100
[ 30.723201] __arm_smccc_smc+0x0/0x2c
[ 30.723272] zynqmp_pm_get_api_version.part.1+0x40/0x68
[ 30.723352] zynqmp_firmware_probe+0xbc/0x298
next prev parent reply other threads:[~2019-12-08 22:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 16:07 [PATCH 0/5] arm64: zynqmp: add firmware device tree node Michael Tretter
2019-10-18 16:07 ` [PATCH 1/5] arm64: zynqmp: Add firmware DT node Michael Tretter
2019-12-08 22:38 ` Guenter Roeck [this message]
2019-12-09 6:42 ` Michal Simek
2019-12-09 7:19 ` Guenter Roeck
2019-12-09 7:48 ` Edgar E. Iglesias
2019-12-09 8:33 ` Michal Simek
2019-12-09 14:32 ` Guenter Roeck
2019-12-09 15:02 ` Michal Simek
2019-12-15 5:28 ` Guenter Roeck
2019-12-16 6:28 ` Michal Simek
2019-12-09 8:36 ` Michal Simek
2019-10-18 16:07 ` [PATCH 2/5] arm64: zynqmp: Add support for zynqmp fpga manager Michael Tretter
2019-10-18 16:07 ` [PATCH 3/5] arm64: zynqmp: Label whole PL part as fpga_full region Michael Tretter
2019-10-18 16:07 ` [PATCH 4/5] arm64: zynqmp: Add support for zynqmp nvmem firmware driver Michael Tretter
2019-10-18 16:07 ` [PATCH 5/5] arm64: zynqmp: Add data cells to access efuse Michael Tretter
2019-10-23 12:30 ` Michal Simek
2019-10-23 12:30 ` [PATCH 0/5] arm64: zynqmp: add firmware device tree node Michal Simek
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=20191208223814.GA21260@roeck-us.net \
--to=linux@roeck-us.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=m.tretter@pengutronix.de \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=qemu-devel@nongnu.org \
--cc=rajan.vaja@xilinx.com \
--cc=rajanv@xilinx.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).