From: Marek Vasut <marex@denx.de>
To: Marcel Ziswiler <marcel@ziswiler.com>,
linux-arm-kernel@lists.infradead.org
Cc: Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Fabio Estevam <festevam@gmail.com>,
Andreas Kemnade <andreas@kemnade.info>,
NXP Linux Team <linux-imx@nxp.com>,
Pascal Zimmermann <pzimmermann@dh-electronics.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Russell King <linux@armlinux.org.uk>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 5/9] ARM: imx_v6_v7_defconfig: build imx sdma driver as module
Date: Mon, 20 Sep 2021 16:52:38 +0200 [thread overview]
Message-ID: <dc987232-8687-a3cc-cc44-9e82e94ddd52@denx.de> (raw)
In-Reply-To: <20210920144938.314588-6-marcel@ziswiler.com>
On 9/20/21 4:49 PM, Marcel Ziswiler wrote:
> From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
>
> Build CONFIG_IMX_SDMA as a module to avoid the following boot issue:
>
> [ 5.214751] imx-sdma 20ec000.sdma: Direct firmware load for
> imx/sdma/sdma-imx6q.bin failed with error -2
> [ 5.215762] imx-sdma 20ec000.sdma: Falling back to sysfs fallback
> for: imx/sdma/sdma-imx6q.bin
Isn't there some ROM-side SDMA firmware baked into the MX6 which is used
as a fallback if loading newer one from filesystem fails ? I suspect the
default ROM firmware might be buggy.
next prev parent reply other threads:[~2021-09-20 14:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 14:49 [PATCH v4 0/9] ARM: prepare and add colibri imx6ull 1gb (emmc) support Marcel Ziswiler
2021-09-20 14:49 ` [PATCH v4 1/9] ARM: imx_v6_v7_defconfig: enable mtd physmap Marcel Ziswiler
2021-10-05 3:22 ` Shawn Guo
2021-09-20 14:49 ` [PATCH v4 2/9] ARM: imx_v6_v7_defconfig: enable fb Marcel Ziswiler
2021-09-20 14:49 ` [PATCH v4 3/9] ARM: imx_v6_v7_defconfig: change snd soc tlv320aic3x to i2c variant Marcel Ziswiler
2021-10-05 3:23 ` Shawn Guo
2021-09-20 14:49 ` [PATCH v4 4/9] ARM: imx_v6_v7_defconfig: rebuild default configuration Marcel Ziswiler
2021-10-05 3:23 ` Shawn Guo
2021-09-20 14:49 ` [PATCH v4 5/9] ARM: imx_v6_v7_defconfig: build imx sdma driver as module Marcel Ziswiler
2021-09-20 14:52 ` Marek Vasut [this message]
2021-09-20 15:55 ` Marcel Ziswiler
2021-09-20 16:14 ` Marek Vasut
2021-09-20 16:50 ` Lucas Stach
2021-10-05 3:24 ` Shawn Guo
2021-09-20 14:49 ` [PATCH v4 6/9] ARM: imx_v6_v7_defconfig: enable bpf syscall and cgroup bpf Marcel Ziswiler
2021-10-05 3:24 ` Shawn Guo
2021-09-20 14:49 ` [PATCH v4 7/9] dt-bindings: arm: fsl: clean-up all toradex boards/modules Marcel Ziswiler
2021-10-05 3:27 ` Shawn Guo
2021-09-20 14:49 ` [PATCH v4 8/9] ARM: dts: colibri-imx6ull-emmc: add device tree Marcel Ziswiler
[not found] ` <20211005032834.GG20743@dragon>
2021-10-05 4:13 ` Marcel Ziswiler
2021-09-20 14:49 ` [PATCH v4 9/9] dt-bindings: arm: fsl: add toradex,colibri-imx6ull-emmc Marcel Ziswiler
2021-10-05 3:28 ` Shawn Guo
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=dc987232-8687-a3cc-cc44-9e82e94ddd52@denx.de \
--to=marex@denx.de \
--cc=andreas@kemnade.info \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marcel.ziswiler@toradex.com \
--cc=marcel@ziswiler.com \
--cc=pzimmermann@dh-electronics.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).