[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e38a63a26d893239d0f82021265fb16c3441786c.camel@sipsolutions.net>
Date: Wed, 15 Jun 2022 23:12:11 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Christian Lamparter <chunkeey@...il.com>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>
Cc: Kalle Valo <kvalo@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
"John W. Linville" <linville@...driver.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org,
Christian Lamparter <chunkeey@....de>,
linux-wireless <linux-wireless@...r.kernel.org>,
Netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH v2] p54: Fix an error handling path in p54spi_probe()
On Wed, 2022-06-15 at 23:03 +0200, Christian Lamparter wrote:
>
> A driver usually loads the firmware in .probe(). It stays around because
> of .suspend()+.resume()
>
Does it, though? the firmware cache thing is a bit odd, it sometimes
seems to me that it only re-requests/loads the firmware when suspending,
and drops the cache when resumed, just in case it's requested inbetween.
johannes
Powered by blists - more mailing lists