On Fri, May 21, 2021 at 8:14 PM Alexandru Ardelean <aardelean@xxxxxxxxxxx> wrote: > > The platform_set_drvdata() call is only useful if we need to retrieve back > the private information. > Since the driver doesn't do that, it's not useful to have it. > > If this is removed, we can also just do a direct return on > devm_gpiochip_add_data(). We don't need to print that this call failed as > there are other ways to log/see this during probe > > Signed-off-by: Alexandru Ardelean <aardelean@xxxxxxxxxxx> > --- > drivers/gpio/gpio-da9052.c | 11 +---------- > 1 file changed, 1 insertion(+), 10 deletions(-) > > diff --git a/drivers/gpio/gpio-da9052.c b/drivers/gpio/gpio-da9052.c > index 9aa59afdcbbf..559188d80c2b 100644 > --- a/drivers/gpio/gpio-da9052.c > +++ b/drivers/gpio/gpio-da9052.c > @@ -196,7 +196,6 @@ static int da9052_gpio_probe(struct platform_device *pdev) > { > struct da9052_gpio *gpio; > struct da9052_pdata *pdata; > - int ret; > > gpio = devm_kzalloc(&pdev->dev, sizeof(*gpio), GFP_KERNEL); > if (!gpio) > @@ -209,15 +208,7 @@ static int da9052_gpio_probe(struct platform_device *pdev) > if (pdata && pdata->gpio_base) > gpio->gp.base = pdata->gpio_base; > > - ret = devm_gpiochip_add_data(&pdev->dev, &gpio->gp, gpio); > - if (ret < 0) { > - dev_err(&pdev->dev, "Could not register gpiochip, %d\n", ret); > - return ret; > - } > - > - platform_set_drvdata(pdev, gpio); > - > - return 0; > + return devm_gpiochip_add_data(&pdev->dev, &gpio->gp, gpio); > } > > static struct platform_driver da9052_gpio_driver = { > -- > 2.31.1 > Applied, thanks! Bart