From: Saravana Kannan <saravanak@google.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Android Kernel Team <kernel-team@android.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] driver core: Avoid pointless deferred probe attempts
Date: Tue, 23 Feb 2021 11:56:10 -0800 [thread overview]
Message-ID: <CAGETcx_BJhR353sbMu2syiwMoep=-oJNAe-GAB_-yAPXGfihKw@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdUo_2WPxDeckhF3nt2+p5eG=mpP84a_fWFZnXyeohqo0g@mail.gmail.com>
On Tue, Feb 23, 2021 at 2:10 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> Hi Saravana,
>
> On Thu, Feb 18, 2021 at 12:51 AM Saravana Kannan <saravanak@google.com> wrote:
> > There's no point in adding a device to the deferred probe list if we
> > know for sure that it doesn't have a matching driver. So, check if a
> > device can match with a driver before adding it to the deferred probe
> > list.
> >
> > Signed-off-by: Saravana Kannan <saravanak@google.com>
>
> Thanks for your patch!
>
> > ---
> > Geert,
> >
> > Can you give this a shot for your I2C DMA issue with fw_devlink=on?
>
> Yes, this makes I2C use DMA again on Salvator-XS during kernel boot-up.
Thanks for testing Geert!
> I haven't run any more elaborate tests on other platforms.
Yeah, this change should only go into 5.13 after it gets tested as
part of driver-core-next.
-Saravana
prev parent reply other threads:[~2021-02-23 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 23:51 [PATCH] driver core: Avoid pointless deferred probe attempts Saravana Kannan
2021-02-18 17:18 ` Rafael J. Wysocki
2021-02-18 17:24 ` Saravana Kannan
2021-02-18 17:58 ` Saravana Kannan
2021-02-25 1:32 ` Saravana Kannan
2021-02-23 10:09 ` Geert Uytterhoeven
2021-02-23 19:56 ` Saravana Kannan [this message]
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='CAGETcx_BJhR353sbMu2syiwMoep=-oJNAe-GAB_-yAPXGfihKw@mail.gmail.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;
as well as URLs for NNTP newsgroup(s).