From: Leonard Crestez <leonard.crestez@nxp.com>
To: Jurgen Lambrecht <J.Lambrecht@TELEVIC.com>,
Robin Gong <yibin.gong@nxp.com>
Cc: Aisheng Dong <aisheng.dong@nxp.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
dl-linux-imx <linux-imx@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: FYI: imx-sdma firmware is not compatible with SLUB slab allocator
Date: Tue, 3 Sep 2019 14:48:46 +0000 [thread overview]
Message-ID: <VI1PR04MB70235FD928F65235B2252C6CEEB90@VI1PR04MB7023.eurprd04.prod.outlook.com> (raw)
In-Reply-To: dc06392b-8242-7d09-e0fe-49fb04849ebb@televic.com
On 03.09.2019 17:32, Jurgen Lambrecht wrote:
> On 9/3/19 7:57 AM, Robin Gong wrote:
>
>>> And that are the last commits on drivers/dma/imx-sdma.c for my 4.19.x+fslc
>>> branch. But I have already tried 5.1.x+fslc, and it also got stuck.
>> Sorry, I can't reproduce your issue on Linux 5.3-rc6 with 'CONFIG_SLOB=y' and
>> SDMA firmware built in kernel, Could you have a try on our imx6ul-14x14-evk
>> board with Linux 5.3-rc6 directly(no any patch needed)?
>
> This works on our own board (with imx6ul)!
Something seems to be wrong with the fslc tree, using 5.1.x+fslc at
latest commit cd1d083333e76e03d16f015c23f1f1b8c8637381 I can reproduce
the issue on imx6ul-14x14-evk board.
Running without SLOB and builtin firmware it's fine.
I couldn't reproduce with latest 4.19.x+fslc (currently at commit
91d5756ab9096bbec256115d1d6b85f5d7139f85), maybe some additional SDMA
patches were applied which fixed this issue?
--
Regards,
Leonard
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-03 14:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 13:35 FYI: imx-sdma firmware is not compatible with SLUB slab allocator Jurgen Lambrecht
2019-08-27 15:04 ` Leonard Crestez
2019-08-28 9:26 ` Jurgen Lambrecht
2019-08-28 14:05 ` Robin Gong
2019-08-29 6:23 ` Jurgen Lambrecht
2019-09-03 5:57 ` Robin Gong
2019-09-03 14:32 ` Jurgen Lambrecht
2019-09-03 14:48 ` Leonard Crestez [this message]
2019-09-04 14:26 ` Jurgen Lambrecht
2019-09-12 6:33 ` Uwe Kleine-König
2019-09-12 2:06 ` Robin Gong
2019-09-12 9:45 ` Jurgen Lambrecht
2019-09-12 12:12 ` Jurgen Lambrecht
2019-09-12 14:19 ` Robin Gong
2019-09-12 14:40 ` Russell King - ARM Linux admin
2019-09-12 14:47 ` Robin Gong
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=VI1PR04MB70235FD928F65235B2252C6CEEB90@VI1PR04MB7023.eurprd04.prod.outlook.com \
--to=leonard.crestez@nxp.com \
--cc=J.Lambrecht@TELEVIC.com \
--cc=aisheng.dong@nxp.com \
--cc=fabio.estevam@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=yibin.gong@nxp.com \
/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).