avr32: Use platform_driver_probe for pdc platform driver
The probe function of the pdc platform driver lives in the init section and so a pdc device that is created after the init section is discarded probably results in an oops. Even if this cannot happen, using platform_driver_probe is cleaner. (If this can happen and should be supported the probe function must live in the devinit section instead.) Signed-off-by: Uwe Kleine-König <ukleinek@strlen.de> Signed-off-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
This commit is contained in:
parent
d6634db8fe
commit
787928e747
|
@ -35,7 +35,6 @@ static int __init pdc_probe(struct platform_device *pdev)
|
|||
}
|
||||
|
||||
static struct platform_driver pdc_driver = {
|
||||
.probe = pdc_probe,
|
||||
.driver = {
|
||||
.name = "pdc",
|
||||
},
|
||||
|
@ -43,6 +42,6 @@ static struct platform_driver pdc_driver = {
|
|||
|
||||
static int __init pdc_init(void)
|
||||
{
|
||||
return platform_driver_register(&pdc_driver);
|
||||
return platform_driver_probe(&pdc_driver, pdc_probe);
|
||||
}
|
||||
arch_initcall(pdc_init);
|
||||
|
|
Loading…
Reference in New Issue