Re: [PATCH] gpio: gpio-bd9571mwv: remove platform_set_drvdata() + cleanup probe

[Bartosz Golaszewski <bgolaszewski@xxxxxxxxxxxx>]

On Fri, May 14, 2021 at 11:26 AM 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-bd9571mwv.c | 11 +----------
>  1 file changed, 1 insertion(+), 10 deletions(-)
>
> diff --git a/drivers/gpio/gpio-bd9571mwv.c b/drivers/gpio/gpio-bd9571mwv.c
> index df6102b57734..9a4d55f703bb 100644
> --- a/drivers/gpio/gpio-bd9571mwv.c
> +++ b/drivers/gpio/gpio-bd9571mwv.c
> @@ -97,25 +97,16 @@ static const struct gpio_chip template_chip = {
>  static int bd9571mwv_gpio_probe(struct platform_device *pdev)
>  {
>         struct bd9571mwv_gpio *gpio;
> -       int ret;
>
>         gpio = devm_kzalloc(&pdev->dev, sizeof(*gpio), GFP_KERNEL);
>         if (!gpio)
>                 return -ENOMEM;
>
> -       platform_set_drvdata(pdev, gpio);
> -
>         gpio->regmap = dev_get_regmap(pdev->dev.parent, NULL);
>         gpio->chip = template_chip;
>         gpio->chip.parent = pdev->dev.parent;
>
> -       ret = devm_gpiochip_add_data(&pdev->dev, &gpio->chip, gpio);
> -       if (ret < 0) {
> -               dev_err(&pdev->dev, "Could not register gpiochip, %d\n", ret);
> -               return ret;
> -       }
> -
> -       return 0;
> +       return devm_gpiochip_add_data(&pdev->dev, &gpio->chip, gpio);
>  }
>
>  static const struct platform_device_id bd9571mwv_gpio_id_table[] = {
> --
> 2.31.1
>

Applied, thanks!
Bartosz