gpio: tps6586x: 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. 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@deviqon.com> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
This commit is contained in:
parent
6e153938b7
commit
cc7af0bfa0
|
@ -76,7 +76,6 @@ static int tps6586x_gpio_probe(struct platform_device *pdev)
|
|||
{
|
||||
struct tps6586x_platform_data *pdata;
|
||||
struct tps6586x_gpio *tps6586x_gpio;
|
||||
int ret;
|
||||
|
||||
pdata = dev_get_platdata(pdev->dev.parent);
|
||||
tps6586x_gpio = devm_kzalloc(&pdev->dev,
|
||||
|
@ -106,16 +105,8 @@ static int tps6586x_gpio_probe(struct platform_device *pdev)
|
|||
else
|
||||
tps6586x_gpio->gpio_chip.base = -1;
|
||||
|
||||
ret = devm_gpiochip_add_data(&pdev->dev, &tps6586x_gpio->gpio_chip,
|
||||
tps6586x_gpio);
|
||||
if (ret < 0) {
|
||||
dev_err(&pdev->dev, "Could not register gpiochip, %d\n", ret);
|
||||
return ret;
|
||||
}
|
||||
|
||||
platform_set_drvdata(pdev, tps6586x_gpio);
|
||||
|
||||
return ret;
|
||||
return devm_gpiochip_add_data(&pdev->dev, &tps6586x_gpio->gpio_chip,
|
||||
tps6586x_gpio);
|
||||
}
|
||||
|
||||
static struct platform_driver tps6586x_gpio_driver = {
|
||||
|
|
Loading…
Reference in New Issue