gpio: mvebu: Remove initcall-based driver initialization
There's no reason to use an initcall to initialize this driver, and regular module_platform_driver() can be used instead. Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com> Reviewed-by: Javier Martinez Canillas <javier@dowhile0.org> Acked-by: Jason Cooper <jason@lakedaemon.net> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
This commit is contained in:
parent
a49f2e748d
commit
dd640039e8
|
@ -736,9 +736,4 @@ static struct platform_driver mvebu_gpio_driver = {
|
|||
},
|
||||
.probe = mvebu_gpio_probe,
|
||||
};
|
||||
|
||||
static int __init mvebu_gpio_init(void)
|
||||
{
|
||||
return platform_driver_register(&mvebu_gpio_driver);
|
||||
}
|
||||
postcore_initcall(mvebu_gpio_init);
|
||||
module_platform_driver(mvebu_gpio_driver);
|
||||
|
|
Loading…
Reference in a new issue