From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Akash Kumar <quic_akakum@quicinc.com>
Cc: "Jing Leng" <jleng@ambarella.com>,
"Felipe Balbi" <balbi@kernel.org>,
"Pratham Pratap " <quic_ppratap@quicinc.com>,
"Jack Pham" <quic_jackp@quicinc.com>,
kernel@quicinc.com, "Wesley Cheng" <quic_wcheng@quicinc.com>,
"Vijayavardhan Vennapusa" <quic_vvreddy@quicinc.com>,
"Krishna Kurapati" <quic_kriskura@quicinc.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: pci-quirks: Skip usb_early_handoff for Renesas PCI USB
Date: Tue, 21 May 2024 10:05:36 +0200 [thread overview]
Message-ID: <2024052134-roundness-foyer-7bfa@gregkh> (raw)
In-Reply-To: <20240521074635.17938-1-quic_akakum@quicinc.com>
On Tue, May 21, 2024 at 01:16:35PM +0530, Akash Kumar wrote:
> Skip usb_early_handoff for the Renesas PCI USB controller due to
> the firmware not being loaded beforehand, which impacts the bootup
> time.
>
> Signed-off-by: Akash Kumar <quic_akakum@quicinc.com>
What commit id does this fix? Should it go to stable kernels?
> ---
> drivers/usb/host/pci-quirks.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/usb/host/pci-quirks.c b/drivers/usb/host/pci-quirks.c
> index 0b949acfa258..a0770ecc0861 100644
> --- a/drivers/usb/host/pci-quirks.c
> +++ b/drivers/usb/host/pci-quirks.c
> @@ -1264,6 +1264,11 @@ static void quirk_usb_early_handoff(struct pci_dev *pdev)
> }
> }
>
> + /* Skip handoff for Renesas PCI USB controller on QCOM SOC */
> + if ((pdev->vendor == PCI_VENDOR_ID_RENESAS) &&
> + (pcie_find_root_port(pdev)->vendor == PCI_VENDOR_ID_QCOM))
Why are all Renesas PCI devices on a QCOM host to be marked this way?
That's a very big hammer for potentially lots of devices. Have you
tested them all?
thanks,
greg k-h
next prev parent reply other threads:[~2024-05-21 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 7:46 [PATCH] USB: pci-quirks: Skip usb_early_handoff for Renesas PCI USB Akash Kumar
2024-05-21 8:05 ` Greg Kroah-Hartman [this message]
[not found] ` <1ceae2a4-0715-4cea-9351-fd98a0017b85@quicinc.com>
2024-05-21 9:36 ` AKASH KUMAR
2024-05-21 9:38 ` Greg Kroah-Hartman
2024-05-22 9:30 ` AKASH KUMAR
2024-05-23 3:00 ` Bjorn Andersson
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=2024052134-roundness-foyer-7bfa@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=jleng@ambarella.com \
--cc=kernel@quicinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_akakum@quicinc.com \
--cc=quic_jackp@quicinc.com \
--cc=quic_kriskura@quicinc.com \
--cc=quic_ppratap@quicinc.com \
--cc=quic_vvreddy@quicinc.com \
--cc=quic_wcheng@quicinc.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