[+cc Geert, who originally came up with "spi_controller"] On Mon, Sep 26, 2022 at 10:29:32PM +0800, Yang Yingliang wrote: > Introduce devm_spi_alloc_controller() to wrap __devm_spi_alloc_controller(), > with this wrapper, the drivers can use it to update to the modern naming. [...] > --- a/include/linux/spi/spi.h > +++ b/include/linux/spi/spi.h > @@ -778,6 +778,12 @@ static inline struct spi_controller *devm_spi_alloc_slave(struct device *dev, > return __devm_spi_alloc_controller(dev, size, true); > } > > +static inline struct spi_controller *devm_spi_alloc_controller(struct device *dev, > + unsigned int size) > +{ > + return __devm_spi_alloc_controller(dev, size, false); > +} > + > extern int spi_register_controller(struct spi_controller *ctlr); > extern int devm_spi_register_controller(struct device *dev, > struct spi_controller *ctlr); This doesn't really make sense I'm afraid. The umbrella term "spi_controller" can refer to either a master or a slave. One has to specify on allocation which of the two is desired. An API which purports to allow allocation of the umbrella term but defaults to a master behind the scenes seems misleading to me. Thanks, Lukas