From: Saravana Kannan <saravanak@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Saravana Kannan <saravanak@google.com>,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
kernel-team@android.com
Subject: [PATCH v1 0/3] Fix dpm_list ordering issue due to fw_devlink optimization
Date: Wed, 1 Jul 2020 12:42:56 -0700 [thread overview]
Message-ID: <20200701194259.3337652-1-saravanak@google.com> (raw)
When commit 93d2e4322aa7 ("of: platform: Batch fwnode parsing when
adding all top level devices") enabled batch processing of fw_devlink to
optimize the parsing time, it caused a suspend/resume regression due to
the use of deferred probing early on at boot.
This series fixes the regression by avoiding the use of deferred probing
when optimizing fw_devlink parsing.
Saravana Kannan (3):
driver core: Don't do deferred probe in parallel with kernel_init
thread
driver core: Rename dev_links_info.defer_sync to defer_hook
driver core: Avoid deferred probe due to fw_devlink_pause/resume()
drivers/base/base.h | 1 -
drivers/base/core.c | 44 ++++++++++++++++++++++++++++++------------
drivers/base/dd.c | 5 -----
include/linux/device.h | 5 +++--
4 files changed, 35 insertions(+), 20 deletions(-)
--
2.27.0.212.ge8ba1cc988-goog
next reply other threads:[~2020-07-01 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 19:42 Saravana Kannan [this message]
2020-07-01 19:42 ` [PATCH v1 1/3] driver core: Don't do deferred probe in parallel with kernel_init thread Saravana Kannan
2020-07-07 15:59 ` Rafael J. Wysocki
2020-07-07 21:54 ` Saravana Kannan
2020-07-01 19:42 ` [PATCH v1 2/3] driver core: Rename dev_links_info.defer_sync to defer_hook Saravana Kannan
2020-07-07 16:02 ` Rafael J. Wysocki
2020-07-01 19:42 ` [PATCH v1 3/3] driver core: Avoid deferred probe due to fw_devlink_pause/resume() Saravana Kannan
2020-07-07 15:56 ` [PATCH v1 0/3] Fix dpm_list ordering issue due to fw_devlink optimization Rafael J. Wysocki
2020-07-08 8:16 ` Geert Uytterhoeven
2020-07-08 17:36 ` Saravana Kannan
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=20200701194259.3337652-1-saravanak@google.com \
--to=saravanak@google.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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
Powered by JetHome