From: Vinod Koul <vkoul@kernel.org>
To: Peter Robinson <pbrobinson@gmail.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Anson Huang <Anson.Huang@nxp.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
Robin Gong <yibin.gong@nxp.com>,
"Angus Ainslie (Purism)" <angus@akkea.ca>,
dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
stable@vger.kernel.org
Subject: Re: [PATCH] dmaengine: imx-sdma: Allow imx8m for imx7 FW revs
Date: Thu, 9 Jun 2022 11:42:02 +0530 [thread overview]
Message-ID: <YqGPMqRGa58lkRNT@matsya> (raw)
In-Reply-To: <20220606161034.3544803-1-pbrobinson@gmail.com>
On 06-06-22, 17:10, Peter Robinson wrote:
> The revision of the imx-sdma IP that is in the i.MX8M series is the
> same is that as that in the i.MX7 series but the imx7d MODULE_FIRMWARE
> directive is wrapped in a condiditional which means it's not defined
> when built for aarch64 SOC_IMX8M platforms and hence you get the
> following errors when the driver loads on imx8m devices:
>
> imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
> imx-sdma 302c0000.dma-controller: external firmware not found, using ROM firmware
>
> Add the SOC_IMX8M into the check so the firmware can load on i.MX8.
Applied, thanks
--
~Vinod
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-06-09 6:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 16:10 [PATCH] dmaengine: imx-sdma: Allow imx8m for imx7 FW revs Peter Robinson
2022-06-06 16:16 ` Fabio Estevam
2022-06-09 6:12 ` Vinod Koul [this message]
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=YqGPMqRGa58lkRNT@matsya \
--to=vkoul@kernel.org \
--cc=Anson.Huang@nxp.com \
--cc=angus@akkea.ca \
--cc=daniel.baluta@nxp.com \
--cc=dmaengine@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=pbrobinson@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stable@vger.kernel.org \
--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