Re: [RFT PATCH v2] spi: bcm2835: reduce the abuse of the GPIO API

[Dan Carpenter <dan.carpenter@xxxxxxxxxx>]

On Fri, Sep 01, 2023 at 02:15:39PM +0200, Linus Walleij wrote:
> On Fri, Sep 1, 2023 at 1:15 PM Bartosz Golaszewski <brgl@xxxxxxxx> wrote:
> 
> > From: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxx>
> >
> > Currently the bcm2835 SPI driver uses functions that are available
> > exclusively to GPIO providers as a way to handle a platform quirk. Let's
> > use a slightly better alternative that avoids poking around in GPIOLIB's
> > internals and use GPIO lookup tables.
> >
> > Link: https://www.spinics.net/lists/linux-gpio/msg36218.html
> > Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxx>
> 
> > +#include <linux/cleanup.h>
> (...)
> > -       struct gpio_chip *chip;
> > +       struct gpiod_lookup_table *lookup __free(kfree) = NULL;
> 
> Whoa!
> This is really neat.

Yeah.  I like this stuff.  It should fix a lot of issues.  In some ways
I prefer this kind of clean up to devm_ managed resources.

> As noted, it will confuse static checkers at no end, but they just have
> to adopt. (CC to Dan C if he now runs into this.)

I think I updated Smatch to parse this correctly.  I've tested on this
patch and it seems to work okay.  There probably will be some fall out
in weird corners of Smatch.  Let me know if you see any problems.

regards,
dan carpenter