From: Umang Jain <uajain@igalia.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lucas De Marchi <demarchi@kernel.org>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-dev@igalia.com, Umang Jain <uajain@igalia.com>
Subject: [RFC PATCH v1 0/3] usb: early: xhci-dbc: Handle out-of-bound
Date: Thu, 4 Jun 2026 20:11:19 +0530 [thread overview]
Message-ID: <20260604144122.962236-1-uajain@igalia.com> (raw)
Small series to handle xhci-xdbc caps if the offset and out-of-bounds
for fixed time boot mappings. Previous discussion is at [1].
However, RFC because it doesn't completely work for me. Patch 3/3
WIP, makes it partially work (xdbc being recognized at host side)
but still something is OFF. 3/3 might contain a clue which we can
probably discuss in reviews.
[1]: https://lore.kernel.org/linux-usb/ab199e7a-c0d4-4150-bbcc-9ab8b18f0725@linux.intel.com/
Umang Jain (3):
usb: early: xhci-dbc: Track early_ioremap size separately
early: usb: xhci-dbc: Handle out of bounds xhci-xdbc capability
WIP: early: xhci-xdbc: Map lower and with 0 offset to partially work
drivers/usb/early/xhci-dbc.c | 77 ++++++++++++++++++++++++++++--------
drivers/usb/early/xhci-dbc.h | 1 +
2 files changed, 61 insertions(+), 17 deletions(-)
--
2.53.0
next reply other threads:[~2026-06-04 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 14:41 Umang Jain [this message]
2026-06-04 14:41 ` [RFC PATCH v1 1/3] usb: early: xhci-dbc: Track early_ioremap size separately Umang Jain
2026-06-04 14:41 ` [RFC PATCH v1 2/3] early: usb: xhci-dbc: Handle out of bounds xhci-xdbc capability Umang Jain
2026-06-05 18:16 ` Mathias Nyman
2026-06-04 14:41 ` [RFC PATCH v1 3/3] WIP: early: xhci-xdbc: Map lower and with 0 offset to partially work Umang Jain
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=20260604144122.962236-1-uajain@igalia.com \
--to=uajain@igalia.com \
--cc=demarchi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.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
all inboxes | Powered by JetHome®