From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Felipe Balbi <balbi@kernel.org>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Ferry Toth <fntoth@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v1 0/3] usb: dwc3: Avoid using reserved EPs
Date: Thu, 16 Jan 2025 17:40:45 +0200 [thread overview]
Message-ID: <20250116154117.148915-1-andriy.shevchenko@linux.intel.com> (raw)
On some platforms (Intel-based and AFAIK ARM-based) the EPs in the gadget
(USB Device Controller mode) may be reserved for some special means, such as
tracing. This series extends DT schema and driver to avoid using those.
Without this the USB gadget mode won't work properly (those devices that
"luckily" allocated the reserved EPs).
Ferry already tested the privately sent PoC of this, but I ask him again to
re-test this version which is slightly different.
Andy Shevchenko (3):
dt-bindings: usb: dwc3: Add a property to reserve endpoints
usb: dwc3: gadget: Add support for snps,reserved-endpoints property
usb: dwc3: gadget: Skip endpoints ep[18]{in,out} on Intel Merrifield
.../devicetree/bindings/usb/snps,dwc3.yaml | 10 +++++
drivers/usb/dwc3/dwc3-pci.c | 9 +++++
drivers/usb/dwc3/gadget.c | 38 ++++++++++++++++++-
3 files changed, 56 insertions(+), 1 deletion(-)
--
2.43.0.rc1.1336.g36b5255a03ac
next reply other threads:[~2025-01-16 15:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 15:40 Andy Shevchenko [this message]
2025-01-16 15:40 ` [PATCH v1 1/3] dt-bindings: usb: dwc3: Add a property to reserve endpoints Andy Shevchenko
2025-01-23 22:09 ` Rob Herring
2025-01-24 14:55 ` Andy Shevchenko
2025-01-16 15:40 ` [PATCH v1 2/3] usb: dwc3: gadget: Add support for snps,reserved-endpoints property Andy Shevchenko
2025-01-16 23:35 ` Thinh Nguyen
2025-01-17 13:32 ` Andy Shevchenko
2025-01-22 1:44 ` Thinh Nguyen
2025-01-22 17:12 ` Andy Shevchenko
2025-01-28 2:39 ` Thinh Nguyen
2025-01-28 16:55 ` Andy Shevchenko
2025-01-30 1:48 ` Thinh Nguyen
2025-01-16 15:40 ` [PATCH v1 3/3] usb: dwc3: gadget: Skip endpoints ep[18]{in,out} on Intel Merrifield Andy Shevchenko
2025-01-16 23:39 ` Thinh Nguyen
2025-01-17 13:33 ` Andy Shevchenko
2025-01-21 23:46 ` Thinh Nguyen
2025-01-21 23:51 ` Thinh Nguyen
2025-01-22 16:24 ` Andy Shevchenko
2025-01-22 16:23 ` Andy Shevchenko
2025-01-28 2:21 ` Thinh Nguyen
2025-01-28 16:50 ` Andy Shevchenko
2025-01-30 1:44 ` Thinh Nguyen
2025-01-16 23:18 ` [PATCH v1 0/3] usb: dwc3: Avoid using reserved EPs Thinh Nguyen
2025-01-17 13:38 ` Andy Shevchenko
2025-01-20 15:02 ` Andy Shevchenko
2025-01-21 23:43 ` Thinh Nguyen
2025-01-22 16:27 ` Andy Shevchenko
2025-01-28 2:25 ` Thinh Nguyen
2025-01-28 16:57 ` Andy Shevchenko
2025-01-17 22:00 ` Ferry Toth
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=20250116154117.148915-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=balbi@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fntoth@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).