| Message ID | 20221101152132.v2.3.Ic9a4f378f73319da323cd55940012fa6b1de24f4@changeid (mailing list archive) |
|---|---|
| State | Accepted |
| Commit | 692a68ad7f3c568359b9f18d966628856fd34ff3 |
| Headers | show |
| Series | [v2,1/5] platform/chrome: cros_ec_lpc: Move mec_init to device probe | expand |
diff --git a/drivers/platform/chrome/cros_ec_debugfs.c b/drivers/platform/chrome/cros_ec_debugfs.c index 4e63adf083ea..21d973fc6be2 100644 --- a/drivers/platform/chrome/cros_ec_debugfs.c +++ b/drivers/platform/chrome/cros_ec_debugfs.c @@ -521,6 +521,7 @@ static struct platform_driver cros_ec_debugfs_driver = { .driver = { .name = DRV_NAME, .pm = &cros_ec_debugfs_pm_ops, + .probe_type = PROBE_PREFER_ASYNCHRONOUS, }, .probe = cros_ec_debugfs_probe, .remove = cros_ec_debugfs_remove,
This driver takes on the order of 40ms to start on some systems. It shouldn't have many cross-device dependencies to race with, nor racy access to shared state with other drivers, so this should be a relatively low risk change. This driver was pinpointed as part of a survey of top slowest initcalls (i.e., are built in, and probing synchronously) on a lab of ChromeOS systems. Signed-off-by: Brian Norris <briannorris@chromium.org> --- (no changes since v1) drivers/platform/chrome/cros_ec_debugfs.c | 1 + 1 file changed, 1 insertion(+)