From: Saravana Kannan <saravanak@google.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree-spec@vger.kernel.org, kernel-team@android.com
Subject: Re: [PATCH v1] schemas: Add schema for post-init-providers
Date: Wed, 6 Mar 2024 12:52:21 -0800 [thread overview]
Message-ID: <CAGETcx83jn-4uhjZ31Y_TUw5kGGS7WahuWPxLCMP=ck8EmNxSQ@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqKGpbwYU2qQDgDQzWm++aDieCLEWaREW1aiDHM9uzM6Ew@mail.gmail.com>
On Wed, Mar 6, 2024 at 5:11 AM Rob Herring <robh@kernel.org> wrote:
>
> On Tue, Mar 5, 2024 at 6:30 PM Saravana Kannan <saravanak@google.com> wrote:
> >
> > The post-init-providers property can be used to break a dependency cycle by
> > marking some provider(s) as a post device initialization provider(s). This
> > allows an OS to do a better job at ordering initialization and
> > suspend/resume of the devices in a dependency cycle.
> >
> > Signed-off-by: Saravana Kannan <saravanak@google.com>
> > ---
> > dtschema/schemas/post-init-providers.yaml | 105 ++++++++++++++++++++++
> > 1 file changed, 105 insertions(+)
> > create mode 100644 dtschema/schemas/post-init-providers.yaml
> >
> > diff --git a/dtschema/schemas/post-init-providers.yaml b/dtschema/schemas/post-init-providers.yaml
> > new file mode 100644
> > index 0000000..92eb9a0
> > --- /dev/null
> > +++ b/dtschema/schemas/post-init-providers.yaml
> > @@ -0,0 +1,105 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +# Copyright (c) 2020, Google LLC. All rights reserved.
>
> 2020? I can fix it up.
Yes, please. Make it 2024.
-Saravana
next prev parent reply other threads:[~2024-03-06 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 0:29 [PATCH v1] schemas: Add schema for post-init-providers Saravana Kannan
2024-03-06 13:11 ` Rob Herring
2024-03-06 20:52 ` Saravana Kannan [this message]
2024-03-06 19:17 ` Simon Glass
2024-03-06 22:22 ` Rob Herring
2024-03-07 20:55 ` Simon Glass
2024-03-08 6:47 ` Saravana Kannan
2024-03-12 22:09 ` Simon Glass
2024-03-14 1: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='CAGETcx83jn-4uhjZ31Y_TUw5kGGS7WahuWPxLCMP=ck8EmNxSQ@mail.gmail.com' \
--to=saravanak@google.com \
--cc=devicetree-spec@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=robh@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 read-only IMAP folder(s) and NNTP newsgroup(s).