From: Felipe Balbi <balbi@kernel.org>
To: Sid Spry <sid@aeam.us>, linux-usb@vger.kernel.org
Subject: Re: mkdir acm.${name} in configfs always fails with "Device or resource busy"
Date: Tue, 25 Aug 2020 08:27:09 +0300 [thread overview]
Message-ID: <87a6yjjnwy.fsf@kernel.org> (raw)
In-Reply-To: <d22c16f3-9fb2-4dd2-b511-5f2b5a975d6b@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
"Sid Spry" <sid@aeam.us> writes:
> On Mon, Aug 24, 2020, at 1:16 AM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> "Sid Spry" <sid@aeam.us> writes:
>> > See title. I'm getting this even when using shell commands, so I don't
>> > think it is my program. Creating anything else, like ncm.usb0, will
>> > work.
>>
>> which kernel version? which usb controller? which platform?
>>
>
> Kernel 5.4.45 compiled for a Raspberry Pi 4, the UDC is a DWC2.
great. Latest v5.4 stable is v5.4.60. There have been a few fixes in
dwc2 and gadget drivers between .45 and .60. Just to rule out a problem
that was already fixed, could you merge v5.4.60 to your kernel and try
again?
> On another device (Allwinner based) I could add one serial gadget
> but not two, and I though this may have been endpoint exhaustion. Now
> I am not so sure.
It could exhaustion of Interrupt-capable endpoints. It depends on how
the gadget and the UDC were configured.
cheers
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]
next prev parent reply other threads:[~2020-08-25 5:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 4:11 mkdir acm.${name} in configfs always fails with "Device or resource busy" Sid Spry
2020-08-24 6:16 ` Felipe Balbi
2020-08-24 19:25 ` Sid Spry
2020-08-25 5:27 ` Felipe Balbi [this message]
2020-09-13 1:53 ` Sid Spry
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=87a6yjjnwy.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sid@aeam.us \
/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).