[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240319105309.7cdfe106@xps-13>
Date: Tue, 19 Mar 2024 10:53:09 +0100
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Manojkiran Eda <manojkiran.eda@...il.com>,
patrick.rudolph@...ements.com, chiawei_wang@...eedtech.com,
ryan_chen@...eedtech.com, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-aspeed@...ts.ozlabs.org,
linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org,
robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
joel@....id.au, andrew@...econstruct.com.au, richard@....at,
vigneshr@...com, jk@...econstruct.com.au, openbmc@...ts.ozlabs.org
Subject: Re: [PATCH v2 2/4] mtd: Replace module_init with subsys_initcall
Hi,
krzysztof.kozlowski@...aro.org wrote on Tue, 19 Mar 2024 10:51:00 +0100:
> On 19/03/2024 10:34, Manojkiran Eda wrote:
> > While engaged in development on the espi kernel device driver[1],
> > I noticed that the espi flash driver, utilizing the mtd subsystem,
> > appears to initialize before the mtdcore subsystem registers the
>
> NAK
>
> You incorrectly ordered your call, so now to fix this you incorrectly
> re-order rest of kernel. No. Fix your code to handle modules, probe
> deferrals and device links.
Agreed. You shall not need this. Maybe just moving the driver to the
right location (spi) might fix it.
Thanks,
Miquèl
Powered by blists - more mailing lists