The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org,
	Biju Das <biju.das.jz@bp.renesas.com>,
	Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [RFC PATCH] usb: host: Default CONFIG_USB_XHCI_RCAR to module
Date: Thu, 7 May 2026 18:20:26 +0200	[thread overview]
Message-ID: <2026050732-discolor-suing-ef2d@gregkh> (raw)
In-Reply-To: <20260507154710.3903732-1-prabhakar.mahadev-lad.rj@bp.renesas.com>

On Thu, May 07, 2026 at 04:47:10PM +0100, Prabhakar wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> 
> On R-Car Gen3 and RZ/G2HMNE SoCs, when CONFIG_USB_XHCI_RCAR is built-in
> and the system boots with an NFS root filesystem, the xHCI controller
> probes before firmware becomes available. As a result, the firmware
> request fails:
> 
>   xhci-renesas-hcd ee000000.usb: Direct firmware load for
>   r8a779x_usb3_v3.dlmem failed with error -2
> 
> Default CONFIG_USB_XHCI_RCAR to module on ARCH_RENESAS so that probing
> is deferred until after the root filesystem is mounted, ensuring that
> the firmware is accessible.
> 
> Configurations explicitly selecting CONFIG_USB_XHCI_RCAR=y are
> unaffected.
> 
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> ---
>  drivers/usb/host/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kconfig
> index 0a277a07cf70..b70e019cc3ac 100644
> --- a/drivers/usb/host/Kconfig
> +++ b/drivers/usb/host/Kconfig
> @@ -90,7 +90,7 @@ config USB_XHCI_RCAR
>  	tristate "xHCI support for Renesas R-Car SoCs"
>  	depends on USB_XHCI_PLATFORM
>  	depends on ARCH_RENESAS || COMPILE_TEST
> -	default ARCH_RENESAS
> +	default m if ARCH_RENESAS

The module type here depends on your root filesystem.  If you are using
nfs for your root, then you always know you need to properly build stuff
into the kernel for modules that need firmware, this shouldn't be a
default thing as NFS surely isn't a default system type anymore.

thanks,

greg k-h

  reply	other threads:[~2026-05-07 16:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 15:47 [RFC PATCH] usb: host: Default CONFIG_USB_XHCI_RCAR to module Prabhakar
2026-05-07 16:20 ` Greg Kroah-Hartman [this message]
2026-05-07 21:07   ` Lad, Prabhakar

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=2026050732-discolor-suing-ef2d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=fabrizio.castro.jz@renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=prabhakar.csengg@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=yoshihiro.shimoda.uh@renesas.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