From: Linus Walleij <linus.walleij@linaro.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Rob Herring <robh@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Saravana Kannan <saravanak@google.com>,
Russell King <linux@armlinux.org.uk>,
John Stultz <john.stultz@linaro.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Subject: Re: [PATCH] amba: Retry adding deferred devices at late_initcall
Date: Wed, 29 Apr 2020 14:26:38 +0200 [thread overview]
Message-ID: <CACRpkdaE7BRnZbBbx2Lk3CoG6uSiCV1dJWMgF9wU0UyHe2QP0Q@mail.gmail.com> (raw)
In-Reply-To: <733e20b1-9592-6941-766b-9f321ad2ace5@samsung.com>
On Wed, Apr 29, 2020 at 8:06 AM Marek Szyprowski
<m.szyprowski@samsung.com> wrote:
> [Me]
> > There are a bit of other differences that have piled up,
> > should we take a quick look at dd.c so there is not something
> > else we're missing? I see some PM code for example.
>
> Well, late initcall based approach is what earlier version of my patch did:
I see, thanks for the context.
> For me it is fine to get back to late initcall based solution, though.
The idea here is to do both/and initcall and timer deferred probe,
not either/or.
And the dd.c core also does both/and.
And then it does some more things, so I was thinking we may be
missing out on some of them?
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-04-29 12:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 21:25 [PATCH] amba: Retry adding deferred devices at late_initcall Rob Herring
2020-04-28 15:51 ` Sudeep Holla
2020-04-28 20:39 ` Linus Walleij
2020-04-29 6:06 ` Marek Szyprowski
2020-04-29 7:33 ` Saravana Kannan
2020-05-04 19:10 ` Ulf Hansson
2020-05-04 19:28 ` Saravana Kannan
2020-05-07 11:44 ` Marek Szyprowski
2020-05-07 17:39 ` Saravana Kannan
2020-05-08 13:41 ` Rob Herring
2020-05-08 19:19 ` Saravana Kannan
2020-04-29 12:26 ` Linus Walleij [this message]
2020-04-29 14:01 ` Rob Herring
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=CACRpkdaE7BRnZbBbx2Lk3CoG6uSiCV1dJWMgF9wU0UyHe2QP0Q@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=geert+renesas@glider.be \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=nsaenzjulienne@suse.de \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=sudeep.holla@arm.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 NNTP newsgroup(s).