From: Saravana Kannan <saravanak@google.com>
To: Saravana Kannan <saravanak@google.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Len Brown <lenb@kernel.org>
Cc: kernel-team@android.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-efi@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: [PATCH v1 0/4] Add post-init-supplier binding to improve suspend/resume stability
Date: Fri, 9 Feb 2024 19:05:43 -0800 [thread overview]
Message-ID: <20240210030549.4048795-1-saravanak@google.com> (raw)
This patch series adds a "post-init-supplier" device tree binding that
can be used to break dependency cycles in device tree and enforce a more
determinstic probe/suspend/resume order. This will also improve the
stability of global async probing and async suspend/resume and allow us
to enable them more easily. Yet another step away from playing initcall
chicken with probing and step towards fully async probing and
suspend/resume.
Patch 3 (the binding docunentation) provide a lot more details and examples.
Saravana Kannan (4):
driver core: Adds flags param to fwnode_link_add()
driver core: Add FWLINK_FLAG_IGNORE to completely ignore a fwnode link
dt-bindings: Add post-init-supplier property
of: property: fw_devlink: Add support for "post-init-supplier"
property
.../bindings/post-init-supplier.yaml | 99 +++++++++++++++++++
MAINTAINERS | 3 +-
drivers/base/core.c | 14 ++-
drivers/firmware/efi/sysfb_efi.c | 2 +-
drivers/of/property.c | 17 +++-
include/linux/fwnode.h | 5 +-
6 files changed, 131 insertions(+), 9 deletions(-)
create mode 100644 Documentation/devicetree/bindings/post-init-supplier.yaml
--
2.43.0.687.g38aa6559b0-goog
next reply other threads:[~2024-02-10 3:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 3:05 Saravana Kannan [this message]
2024-02-10 3:05 ` [PATCH v1 1/4] driver core: Adds flags param to fwnode_link_add() Saravana Kannan
2024-02-10 3:05 ` [PATCH v1 2/4] driver core: Add FWLINK_FLAG_IGNORE to completely ignore a fwnode link Saravana Kannan
2024-02-10 3:05 ` [PATCH v1 3/4] dt-bindings: Add post-init-supplier property Saravana Kannan
2024-02-10 11:26 ` Rob Herring
2024-02-12 21:08 ` Saravana Kannan
2024-02-10 11:29 ` Rob Herring
2024-02-11 14:52 ` Krzysztof Kozlowski
2024-02-12 21:08 ` Saravana Kannan
2024-02-10 3:05 ` [PATCH v1 4/4] of: property: fw_devlink: Add support for "post-init-supplier" property 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=20240210030549.4048795-1-saravanak@google.com \
--to=saravanak@google.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ardb@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djrscally@gmail.com \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=kernel-team@android.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).