From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218977] New: new dtb break orangepi's usb gadget
Date: Sun, 23 Jun 2024 09:15:13 +0000 [thread overview]
Message-ID: <bug-218977-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218977
Bug ID: 218977
Summary: new dtb break orangepi's usb gadget
Product: Drivers
Version: 2.5
Hardware: ARM
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: plusls@qq.com
Regression: No
I use Armbian in my orangepi one board, and I use the usb gadget to simulate
keyboard and mouse.
It works on Armbian_23.11.1, but it break in Armbian_24.5.1.
After some time, I found out that it is cause by linux kernel commit:
b13d48408e9f0aa80f3d9f93960aa49bd0da7af8, when I remove the "phys" property,
the usb gadget works again.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2024-06-23 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 9:15 bugzilla-daemon [this message]
2024-06-25 5:27 ` [Bug 218977] new dtb break orangepi's usb gadget bugzilla-daemon
2024-06-25 6:22 ` bugzilla-daemon
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=bug-218977-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.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