[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1440592108-3740-17-git-send-email-holler@ahsoftware.de>
Date: Wed, 26 Aug 2015 14:28:28 +0200
From: Alexander Holler <holler@...oftware.de>
To: linux-kernel@...r.kernel.org
Cc: linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
Greg KH <gregkh@...uxfoundation.org>,
Russel King <linux@....linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Grant Likely <grant.likely@...aro.org>,
Tomeu Vizoso <tomeu.vizoso@...labora.com>,
Alexander Holler <holler@...oftware.de>,
Kishon Vijay Abraham I <kishon@...com>
Subject: [PATCH 16/16] phy: phy-core: fix initcall level
The phy-core has to be initialized before other dependent usb-drivers,
otherwise a crash might occur.
Currently phy_core_init() is called in the initcall-level device, which is
the same level where most usb-drivers will end up. By luck this seemed to
have been called most of the time before other usb-drivers without having
been explicitly enforced. But if phy_core_init() is not called before a
dependent driver, a null-pointer exception might occur (e.g. because the
phy device class isn't registered).
To fix this, phy_core_init() is moved to the initcall-level fs (right
before the standard initcall level device).
Signed-off-by: Alexander Holler <holler@...oftware.de>
---
drivers/phy/phy-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c
index fc48fac..4945029 100644
--- a/drivers/phy/phy-core.c
+++ b/drivers/phy/phy-core.c
@@ -930,7 +930,7 @@ static int __init phy_core_init(void)
return 0;
}
-module_init(phy_core_init);
+fs_initcall_sync(phy_core_init);
static void __exit phy_core_exit(void)
{
--
2.1.0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists