linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Marcel Ziswiler <marcel.ziswiler@toradex.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Cc: "enric.balletbo@collabora.com" <enric.balletbo@collabora.com>,
	"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
	"agx@sigxcpu.org" <agx@sigxcpu.org>,
	"krzk@kernel.org" <krzk@kernel.org>,
	"biju.das.jz@bp.renesas.com" <biju.das.jz@bp.renesas.com>,
	"olof@lixom.net" <olof@lixom.net>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"geert+renesas@glider.be" <geert+renesas@glider.be>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"will@kernel.org" <will@kernel.org>
Subject: Re: [PATCH v1 05/14] arm64: defconfig: build imx-sdma as a module
Date: Fri, 14 Jan 2022 17:24:02 +0100	[thread overview]
Message-ID: <d2666a27-a420-5808-6b78-ae77468dae3d@i2se.com> (raw)
In-Reply-To: <0d9e38ad27cf0bebc73e104d8ea462e7cf319e40.camel@toradex.com>

Hi Marcel,

Am 14.01.22 um 14:39 schrieb Marcel Ziswiler:
> Hi Stefan
>
> On Thu, 2022-01-13 at 19:42 +0100, Stefan Wahren wrote:
>> Hi Marcel,
>>
>> Am 07.01.22 um 19:03 schrieb Marcel Ziswiler:
>>> From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
>>>
>>> This avoids firmware load error and sysfs fallback reported as follows:
>>>
>>> [    0.199448] imx-sdma 302c0000.dma-controller: Direct firmware load
>>>  for imx/sdma/sdma-imx7d.bin failed with error -2
>>> [    0.199487] imx-sdma 302c0000.dma-controller: Falling back to sysfs
>>>  fallback for: imx/sdma/sdma-imx7d.bin
>> unfortunately this isn't an explanation why this solve the issue. It
>> looks like that the SDMA firmware is not available for the kernel. Build
>> the driver as a module hide the issue and just load it if the rootfs is
>> available.
> Well, it seems to default to some built-in firmware which, unfortunately, might have some severe known errata
> anyway.
can you please explain what you mean with built-in firmware? AFAIK there
is a firmware in the SoC ROM, but there is also the option to append
firmware files to the kernel image (regardless of initramfs and so on).
For instance the NXP vendor kernel of the i.MX6ULL (uses the same driver
with a different firmware file) appended the necessary firmware per
default. But yes, the external firmware should be preferred.
>
>> What makes you sure that the driver is not critical for other boards
>> during boot?
> That is a good question. I remember that there was some more discussion back when I proposed the same change
> for imx_v6_v7_defconfig in the 32-bit Arm world. While nobody was able to fully answer it all it did get
> accepted by the i.MX maintainer back in the day [1]. I will mention that in v2.

Okay, in this case the change should be fine.

Thanks

>
> [1] https://lore.kernel.org/lkml/20210920144938.314588-6-marcel@ziswiler.com/
>
> Thanks for your review.
>
>> Best regards
>>
>>> Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
>>> ---
>>>
>>>  arch/arm64/configs/defconfig | 2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
>>> index 3c8106c5776a..a18785a827dc 100644
>>> --- a/arch/arm64/configs/defconfig
>>> +++ b/arch/arm64/configs/defconfig
>>> @@ -915,7 +915,7 @@ CONFIG_DMADEVICES=y
>>>  CONFIG_DMA_BCM2835=y
>>>  CONFIG_DMA_SUN6I=m
>>>  CONFIG_FSL_EDMA=y
>>> -CONFIG_IMX_SDMA=y
>>> +CONFIG_IMX_SDMA=m
>>>  CONFIG_K3_DMA=y
>>>  CONFIG_MV_XOR=y
>>>  CONFIG_MV_XOR_V2=y
> Cheers
>
> Marcel
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel


  reply	other threads:[~2022-01-14 16:24 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 18:03 [PATCH v1 00/14] arm64: prepare and add verdin imx8m mini support Marcel Ziswiler
2022-01-07 18:03 ` [PATCH v1 01/14] arm64: dts: imx8mm: fix strange hex notation Marcel Ziswiler
2022-01-10 23:58   ` Laurent Pinchart
2022-01-07 18:03 ` [PATCH v1 02/14] dt-bindings: gpio: fix gpio-hog example Marcel Ziswiler
2022-01-12  1:58   ` Rob Herring
2022-01-07 18:03 ` [PATCH v1 03/14] arm64: defconfig: rebuild default configuration Marcel Ziswiler
2022-01-10  8:39   ` Krzysztof Kozlowski
2022-01-14 13:24     ` Marcel Ziswiler
2022-01-07 18:03 ` [PATCH v1 04/14] arm64: defconfig: enable bpf/cgroup firewalling Marcel Ziswiler
2022-01-10 19:30   ` Song Liu
2022-01-07 18:03 ` [PATCH v1 05/14] arm64: defconfig: build imx-sdma as a module Marcel Ziswiler
2022-01-13 18:42   ` Stefan Wahren
2022-01-14 13:39     ` Marcel Ziswiler
2022-01-14 16:24       ` Stefan Wahren [this message]
2022-01-14 16:30         ` Marcel Ziswiler
2022-01-07 18:03 ` [PATCH v1 06/14] arm64: defconfig: build r8169 " Marcel Ziswiler
2022-01-10  8:40   ` Krzysztof Kozlowski
2022-01-14 13:25     ` Marcel Ziswiler
2022-01-07 18:03 ` [PATCH v1 07/14] arm64: defconfig: build ads1015 adc driver " Marcel Ziswiler
2022-01-10  8:41   ` Krzysztof Kozlowski
2022-01-07 18:03 ` [PATCH v1 08/14] arm64: defconfig: build lm75 temperature sensor " Marcel Ziswiler
2022-01-10  8:41   ` Krzysztof Kozlowski
2022-01-07 18:03 ` [PATCH v1 09/14] arm64: defconfig: build mcp251xfd can " Marcel Ziswiler
2022-01-07 18:03 ` [PATCH v1 10/14] arm64: defconfig: build sdio mwifiex " Marcel Ziswiler
2022-01-07 18:03 ` [PATCH v1 11/14] arm64: defconfig: build nxp bluetooth as modules Marcel Ziswiler
2022-01-07 18:03 ` [PATCH v1 12/14] arm64: defconfig: build nuvoton nau8822 as module Marcel Ziswiler
2022-01-07 18:03 ` [PATCH v1 13/14] dt-bindings: arm: fsl: add toradex,verdin-imx8mm et al Marcel Ziswiler
2022-01-12  1:58   ` Rob Herring
2022-01-07 18:03 ` [PATCH v1 14/14] arm64: dts: freescale: add initial support for verdin imx8m mini Marcel Ziswiler
2022-01-10  8:47   ` Krzysztof Kozlowski
2022-01-14 13:28     ` Marcel Ziswiler

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=d2666a27-a420-5808-6b78-ae77468dae3d@i2se.com \
    --to=stefan.wahren@i2se.com \
    --cc=agx@sigxcpu.org \
    --cc=arnd@arndb.de \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=enric.balletbo@collabora.com \
    --cc=geert+renesas@glider.be \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel.ziswiler@toradex.com \
    --cc=marek.vasut@gmail.com \
    --cc=olof@lixom.net \
    --cc=shawnguo@kernel.org \
    --cc=will@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).