Hello Mark, > On Thu, Sep 19, 2019 at 07:23:50PM +0200, Alexandre Belloni wrote: >> On 19/09/2019 17:03:15+0100, Mark Brown wrote: > >> > This is going to break any system where we use both a GPIO chip select >> > and chip select 0. Ideally we'd try to figure out an unused chip select >> > to use here... > >> The point is that this use case is already broken and this patch fixes >> the crash and is easily backportable. > >> Fixing the CS + gpio CS should probably be done in a separate patch. > > If the GPIO is overlaid on any of the existing slots (except GPIO 0) > then it'll cause GPIO 0 to start toggling. I'm not convinced that the > code doesn't currently support that. Actually, the current code is not designed to mix CS and gpio CS, so this patch doesn't introduce any regression on this side. But after going further in the details of the driver, this patch could cause a regression for on the old controllers. I also found other issues in this driver in the chip select management. So I will send a new series fixing all of it. Gregory -- Gregory Clement, Bootlin Embedded Linux and Kernel engineering http://bootlin.com
