From: Saravana Kannan <saravanak@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Len Brown <lenb@kernel.org>
Cc: Saravana Kannan <saravanak@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-acpi@vger.kernel.org,
Ji Luo <ji.luo@nxp.com>
Subject: [PATCH v1 4/4] of: platform: Batch fwnode parsing when adding all top level devices
Date: Thu, 14 May 2020 22:35:00 -0700 [thread overview]
Message-ID: <20200515053500.215929-5-saravanak@google.com> (raw)
In-Reply-To: <20200515053500.215929-1-saravanak@google.com>
The fw_devlink_pause() and fw_devlink_resume() APIs allow batching the
parsing of the device tree nodes when a lot of devices are added. This
will significantly cut down parsing time (as much a 1 second on some
systems). So, use them when adding devices for all the top level device
tree nodes in a system.
Signed-off-by: Saravana Kannan <saravanak@google.com>
---
drivers/of/platform.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/of/platform.c b/drivers/of/platform.c
index 3371e4a06248..55d719347810 100644
--- a/drivers/of/platform.c
+++ b/drivers/of/platform.c
@@ -538,7 +538,9 @@ static int __init of_platform_default_populate_init(void)
}
/* Populate everything else. */
+ fw_devlink_pause();
of_platform_default_populate(NULL, NULL, NULL);
+ fw_devlink_resume();
return 0;
}
--
2.26.2.761.g0e0b3e54be-goog
next prev parent reply other threads:[~2020-05-15 5:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 5:34 [PATCH v1 0/4] Optimize fw_devlink parsing Saravana Kannan
2020-05-15 5:34 ` [PATCH v1 1/4] driver core: Move code to the right part of the file Saravana Kannan
2020-05-15 5:34 ` [PATCH v1 2/4] driver core: Look for waiting consumers only for a fwnode's primary device Saravana Kannan
2020-05-15 5:34 ` [PATCH v1 3/4] driver core: fw_devlink: Add support for batching fwnode parsing Saravana Kannan
2020-05-15 5:35 ` Saravana Kannan [this message]
[not found] ` <CGME20200519062510eucas1p27bc59da66e1b77534855103a27f87452@eucas1p2.samsung.com>
2020-05-19 6:25 ` [PATCH v1 4/4] of: platform: Batch fwnode parsing when adding all top level devices Marek Szyprowski
2020-05-19 6:48 ` Saravana Kannan
2020-05-19 7:11 ` Marek Szyprowski
2020-05-19 10:32 ` Marek Szyprowski
2020-05-19 18:02 ` Saravana Kannan
2020-05-20 4:21 ` Marek Szyprowski
2020-06-17 12:20 ` Geert Uytterhoeven
2020-06-17 18:36 ` Saravana Kannan
2020-06-18 7:31 ` Geert Uytterhoeven
2020-06-18 23:00 ` Saravana Kannan
2020-06-19 12:24 ` Geert Uytterhoeven
2020-06-19 20:07 ` Saravana Kannan
2020-06-20 2:32 ` Saravana Kannan
2020-06-22 15:49 ` Geert Uytterhoeven
2020-06-24 23:22 ` Saravana Kannan
2020-05-15 8:52 ` [PATCH v1 0/4] Optimize fw_devlink parsing Saravana Kannan
2020-05-15 14:36 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200515053500.215929-5-saravanak@google.com \
--to=saravanak@google.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ji.luo@nxp.com \
--cc=kernel-team@android.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).