Skip to contentSkip to conversation

gpio: sama5d2-piobu: remove platform_set_drvdata() + cleanup probe

PATCH In review Alexandru Ardelean 1 participant 2 messages Jul 7, 2021 – Jul 8, 2021

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 gpio: sama5d2-piobu: remove platform_set_drvdata() + cleanup probe

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.

This change also changes the probe order a bit, moving the devm_gpiochip_add_data() as the last call. This means that when the gpiochip is registered [and available to consumers], it should be initialized.

It's still possible that the devm_gpiochip_add_data() call could fail, leaving the chip in a partially initialized state, but that was possible even before this change; it was just some other partially initialized state.

---
 drivers/gpio/gpio-sama5d2-piobu.c | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)
drivers/gpio/gpio-sama5d2-piobu.c +1 -8
index b7c950658170..dfaa069b1466 100644
@@ -189,7 +189,6 @@ static int sama5d2_piobu_probe(struct platform_device *pdev)
 	if (!piobu)
 		return -ENOMEM;
 
-	platform_set_drvdata(pdev, piobu);
 	piobu->chip.label = pdev->name;
 	piobu->chip.parent = &pdev->dev;
 	piobu->chip.of_node = pdev->dev.of_node;
@@ -210,12 +209,6 @@ static int sama5d2_piobu_probe(struct platform_device *pdev)
 		return PTR_ERR(piobu->regmap);
 	}
 
-	ret = devm_gpiochip_add_data(&pdev->dev, &piobu->chip, piobu);
-	if (ret) {
-		dev_err(&pdev->dev, "Failed to add gpiochip %d\n", ret);
-		return ret;
-	}
-
 	for (i = 0; i < PIOBU_NUM; ++i) {
 		ret = sama5d2_piobu_setup_pin(&piobu->chip, i);
 		if (ret) {
@@ -225,7 +218,7 @@ static int sama5d2_piobu_probe(struct platform_device *pdev)
 		}
 	}
 
-	return 0;
+	return devm_gpiochip_add_data(&pdev->dev, &piobu->chip, piobu);
 }
 
 static const struct of_device_id sama5d2_piobu_ids[] = {
Signature · 1 line
2.31.1
#1 lore raw
Quoted 10 lines · Alexandru Ardelean

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.

This change also changes the probe order a bit, moving the devm_gpiochip_add_data() as the last call. This means that when the gpiochip is registered [and available to consumers], it should be initialized.

Quoted 5 lines

It's still possible that the devm_gpiochip_add_data() call could fail, leaving the chip in a partially initialized state, but that was possible even before this change; it was just some other partially initialized state.

Please disregard this.
It seems I have not taken into consideration the fact that interrupts are enabled after the gpiochip is registered.

Quoted 42 lines
---
 drivers/gpio/gpio-sama5d2-piobu.c | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)
drivers/gpio/gpio-sama5d2-piobu.c +1 -9
index b7c950658170..dfaa069b1466 100644
@@ -189,7 +189,6 @@ static int sama5d2_piobu_probe(struct platform_device *pdev)
        if (!piobu)
                return -ENOMEM;
 
-       platform_set_drvdata(pdev, piobu);
        piobu->chip.label = pdev->name;
        piobu->chip.parent = &pdev->dev;
        piobu->chip.of_node = pdev->dev.of_node;
@@ -210,12 +209,6 @@ static int sama5d2_piobu_probe(struct platform_device *pdev)
                return PTR_ERR(piobu->regmap);
        }
 
-       ret = devm_gpiochip_add_data(&pdev->dev, &piobu->chip, piobu);
-       if (ret) {
-               dev_err(&pdev->dev, "Failed to add gpiochip %d\n", ret);
-               return ret;
-       }
-
        for (i = 0; i < PIOBU_NUM; ++i) {
                ret = sama5d2_piobu_setup_pin(&piobu->chip, i);
                if (ret) {
@@ -225,7 +218,7 @@ static int sama5d2_piobu_probe(struct platform_device *pdev)
                }
        }
 
-       return 0;
+       return devm_gpiochip_add_data(&pdev->dev, &piobu->chip, piobu);
 }
 
 static const struct of_device_id sama5d2_piobu_ids[] = {
--

2.31.1