All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Anand Moon <linux.amoon@gmail.com>
Cc: "Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Manivannan Sadhasivam" <mani@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Heiko Stuebner" <heiko@sntech.de>,
	"Shawn Lin" <shawn.lin@rock-chips.com>,
	"Hans Zhang" <18255117159@163.com>,
	"Nicolas Frattaroli" <nicolas.frattaroli@collabora.com>,
	"Wilfred Mallawa" <wilfred.mallawa@wdc.com>,
	"open list:PCI NATIVE HOST BRIDGE AND ENDPOINT DRIVERS"
	<linux-pci@vger.kernel.org>,
	"moderated list:ARM/Rockchip SoC support"
	<linux-arm-kernel@lists.infradead.org>,
	"open list:ARM/Rockchip SoC support"
	<linux-rockchip@lists.infradead.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	Grimmauld <grimmauld@grimmauld.de>
Subject: Re: [PATCH v3] PCI: dw-rockchip: Enable async probe by default
Date: Thu, 26 Feb 2026 13:06:58 +0100	[thread overview]
Message-ID: <aaA3YuIOK_Q0MPi-@ryzen> (raw)
In-Reply-To: <20260226101032.1042-1-linux.amoon@gmail.com>

On Thu, Feb 26, 2026 at 03:40:23PM +0530, Anand Moon wrote:
> Rockchip DWC PCIe driver currently performs synchronous link training for
> combo PHYs (PCIe 3.0/2.0 and SATA 3.0) during boot. This process waits for
> the link to be fully established, adding several milliseconds to the boot
> sequence. To optimize boot time, this change enables asynchronous probing,
> allowing link establishment to proceed in the background while the kernel
> continues probing other devices.
> 
> Cc: Grimmauld <grimmauld@grimmauld.de>
> Cc: Niklas Cassel <cassel@kernel.org>
> Tested-by: Grimmauld <grimmauld@grimmauld.de>
> Signed-off-by: Anand Moon <linux.amoon@gmail.com>

Reviewed-by: Niklas Cassel <cassel@kernel.org>


WARNING: multiple messages have this Message-ID (diff)
From: Niklas Cassel <cassel@kernel.org>
To: Anand Moon <linux.amoon@gmail.com>
Cc: "Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Manivannan Sadhasivam" <mani@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Heiko Stuebner" <heiko@sntech.de>,
	"Shawn Lin" <shawn.lin@rock-chips.com>,
	"Hans Zhang" <18255117159@163.com>,
	"Nicolas Frattaroli" <nicolas.frattaroli@collabora.com>,
	"Wilfred Mallawa" <wilfred.mallawa@wdc.com>,
	"open list:PCI NATIVE HOST BRIDGE AND ENDPOINT DRIVERS"
	<linux-pci@vger.kernel.org>,
	"moderated list:ARM/Rockchip SoC support"
	<linux-arm-kernel@lists.infradead.org>,
	"open list:ARM/Rockchip SoC support"
	<linux-rockchip@lists.infradead.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	Grimmauld <grimmauld@grimmauld.de>
Subject: Re: [PATCH v3] PCI: dw-rockchip: Enable async probe by default
Date: Thu, 26 Feb 2026 13:06:58 +0100	[thread overview]
Message-ID: <aaA3YuIOK_Q0MPi-@ryzen> (raw)
In-Reply-To: <20260226101032.1042-1-linux.amoon@gmail.com>

On Thu, Feb 26, 2026 at 03:40:23PM +0530, Anand Moon wrote:
> Rockchip DWC PCIe driver currently performs synchronous link training for
> combo PHYs (PCIe 3.0/2.0 and SATA 3.0) during boot. This process waits for
> the link to be fully established, adding several milliseconds to the boot
> sequence. To optimize boot time, this change enables asynchronous probing,
> allowing link establishment to proceed in the background while the kernel
> continues probing other devices.
> 
> Cc: Grimmauld <grimmauld@grimmauld.de>
> Cc: Niklas Cassel <cassel@kernel.org>
> Tested-by: Grimmauld <grimmauld@grimmauld.de>
> Signed-off-by: Anand Moon <linux.amoon@gmail.com>

Reviewed-by: Niklas Cassel <cassel@kernel.org>

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2026-02-26 12:07 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 10:10 [PATCH v3] PCI: dw-rockchip: Enable async probe by default Anand Moon
2026-02-26 10:10 ` Anand Moon
2026-02-26 12:06 ` Niklas Cassel [this message]
2026-02-26 12:06   ` Niklas Cassel
2026-03-02 15:59 ` Hans Zhang
2026-03-02 15:59   ` Hans Zhang
2026-03-03  1:01 ` Shawn Lin
2026-03-03  1:01   ` Shawn Lin
2026-03-04  6:48 ` Manivannan Sadhasivam
2026-03-04  6:48   ` Manivannan Sadhasivam
2026-03-10 13:41   ` Robin Murphy
2026-03-10 13:41     ` Robin Murphy
2026-03-10 15:30     ` Manivannan Sadhasivam
2026-03-10 15:30       ` Manivannan Sadhasivam
2026-03-10 21:03       ` Robin Murphy
2026-03-10 21:03         ` Robin Murphy
2026-03-11  0:43         ` Danilo Krummrich
2026-03-11  0:43           ` Danilo Krummrich
2026-03-25  3:44           ` Dmitry Torokhov
2026-03-25  3:44             ` Dmitry Torokhov
2026-03-25  6:36             ` Lukas Wunner
2026-03-25  6:36               ` Lukas Wunner
2026-03-11  5:24         ` Manivannan Sadhasivam
2026-03-11  5:24           ` Manivannan Sadhasivam
2026-03-11  7:56           ` Lukas Wunner
2026-03-11 11:46           ` Danilo Krummrich
2026-03-11 11:46             ` Danilo Krummrich
2026-03-11 12:13             ` Niklas Cassel
2026-03-11 12:13               ` Niklas Cassel
2026-03-11 12:28             ` Manivannan Sadhasivam
2026-03-11 12:28               ` Manivannan Sadhasivam
2026-03-11 21:09               ` Danilo Krummrich
2026-03-11 21:09                 ` Danilo Krummrich
2026-03-12  1:33                 ` Shawn Lin
2026-03-12  1:33                   ` Shawn Lin
2026-03-12 11:40                   ` Anand Moon
2026-03-12 11:40                     ` Anand Moon
2026-03-12 11:54                     ` Danilo Krummrich
2026-03-12 11:54                       ` Danilo Krummrich
2026-03-13  9:26                       ` Anand Moon
2026-03-13  9:26                         ` Anand Moon
2026-03-12 12:48                 ` Robin Murphy
2026-03-12 12:48                   ` Robin Murphy
2026-03-12 12:59                   ` Danilo Krummrich
2026-03-12 12:59                     ` Danilo Krummrich
2026-03-13 13:15                     ` Robin Murphy
2026-03-13 13:15                       ` Robin Murphy
2026-03-13 14:39                       ` Danilo Krummrich
2026-03-13 14:39                         ` Danilo Krummrich
2026-03-13 17:36                         ` Robin Murphy
2026-03-13 17:36                           ` Robin Murphy
2026-03-14  5:12                           ` Anand Moon
2026-03-14  5:12                             ` Anand Moon
2026-03-17  6:24                             ` Anand Moon
2026-03-17  6:24                               ` Anand Moon
2026-03-13 14:05                     ` Manivannan Sadhasivam
2026-03-13 14:05                       ` Manivannan Sadhasivam
2026-03-13  9:25                   ` Anand Moon
2026-03-13  9:25                     ` Anand Moon
2026-03-25  4:13                   ` Dmitry Torokhov
2026-03-25  4:13                     ` Dmitry Torokhov
2026-03-25 15:01                     ` Robin Murphy
2026-03-25 15:01                       ` Robin Murphy
2026-03-25 15:23                       ` Dmitry Torokhov
2026-03-25 15:23                         ` Dmitry Torokhov
2026-03-25 15:13                     ` Danilo Krummrich
2026-03-25 15:13                       ` Danilo Krummrich
2026-03-25 15:26                       ` Dmitry Torokhov
2026-03-25 15:26                         ` Dmitry Torokhov
2026-03-25 18:24                         ` Anand Moon
2026-03-25 18:24                           ` Anand Moon
2026-03-11 12:32   ` Manivannan Sadhasivam
2026-03-11 12:32     ` Manivannan Sadhasivam

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=aaA3YuIOK_Q0MPi-@ryzen \
    --to=cassel@kernel.org \
    --cc=18255117159@163.com \
    --cc=bhelgaas@google.com \
    --cc=grimmauld@grimmauld.de \
    --cc=heiko@sntech.de \
    --cc=kwilczynski@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux.amoon@gmail.com \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=nicolas.frattaroli@collabora.com \
    --cc=robh@kernel.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=wilfred.mallawa@wdc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.