From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-usb@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/2] usb: host: xhci-rcar: Avoid repeated matching
Date: Wed, 3 Jun 2026 17:17:08 +0200 [thread overview]
Message-ID: <cover.1780499433.git.geert+renesas@glider.be> (raw)
Hi all,
On R-Car Gen2 and Gen3, the .plat_start() callback checks the XHCI's
controller compatible value on each call, which happens multiple
times during the lifetime of the device. This series fixes that by
using separate .plat_start() callbacks, reducing source and binary size
in the process.
This has been tested on R-Car H2 (Lager, disable pci2 first), and R-Car
H3 ES2.0 (Salvator-XS).
Thanks for your comments
Geert Uytterhoeven (2):
usb: host: xhci-rcar: Remove SET_XHCI_PLAT_PRIV_FOR_RCAR() macro
usb: host: xhci-rcar: Split R-Car Gen2 and Gen3 .plat_start() handling
drivers/usb/host/xhci-rcar.c | 70 +++++++++++++++++-------------------
1 file changed, 33 insertions(+), 37 deletions(-)
--
2.43.0
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2026-06-03 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 15:17 Geert Uytterhoeven [this message]
2026-06-03 15:17 ` [PATCH 1/2] usb: host: xhci-rcar: Remove SET_XHCI_PLAT_PRIV_FOR_RCAR() macro Geert Uytterhoeven
2026-06-03 15:17 ` [PATCH 2/2] usb: host: xhci-rcar: Split R-Car Gen2 and Gen3 .plat_start() handling Geert Uytterhoeven
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=cover.1780499433.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=wsa+renesas@sang-engineering.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