[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKaHn9JM-KEiz3_Btsz8_fr7hcZ2Sm8B64VyLvgpvKK-NKco3w@mail.gmail.com>
Date: Fri, 30 Apr 2021 16:49:35 +0800
From: Art Nikpal <email2tema@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: Neil Armstrong <narmstrong@...libre.com>,
Kevin Hilman <khilman@...libre.com>, jbrunet@...libre.com,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
dri-devel@...ts.freedesktop.org, linux-spi@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-amlogic@...ts.infradead.org, linux-kernel@...r.kernel.org,
Christian Hewitt <christianshewitt@...il.com>,
Artem Lapkin <art@...das.com>, nick@...das.com,
Gouwa Wang <gouwa@...das.com>
Subject: Re: [PATCH] SPI: meson-spifc add missed calls to remove function
Yep! but
if i try call spi_master_put(master) or spi_unregister_controller(master);
it's made Segmentation fault for me
what's wrong - may be somebody can help me
On Mon, Apr 26, 2021 at 7:57 PM Mark Brown <broonie@...nel.org> wrote:
>
> On Sat, Apr 24, 2021 at 07:57:19AM +0800, Art Nikpal wrote:
>
> > > I would expect the driver to unregister the controller at the start of
> > > the remove function, suspend doesn't really make sense here
>
> > It's strange - But without spi_master_suspend i have randomly stucks when i
> > try unload this module - as was written before
> > i was test it (load/unload module in loop) and for me suspend make sense
> > here
>
> > If anybody has another solution - or real problem not here - please write
> > to me the right way!
>
> As I said above unregister the controller at the start of the remove
> function.
Powered by blists - more mailing lists