From: Alan Stern <stern@rowland.harvard.edu>
To: "Andrew P. Lentvorski" <bsder@allcaps.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: Unable to set "iInterface" in usb gadget via configfs
Date: Wed, 15 Jan 2020 10:14:58 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44L0.2001151011520.1788-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <994f33ae-fa5f-460c-67c8-92fc5352ebae@allcaps.org>
On Tue, 14 Jan 2020, Andrew P. Lentvorski wrote:
> I've been trying to report what I think is a bug, but I can't seem to
> get through to the mailing list. If these are coming through
> duplicated, please let me know so I can quit sending them.
I don't think any earlier messages in this thread made it through the
mailing list, but this one definitely did.
> Thanks,
> -a
>
>
> > I've been trying to set "iInterface" in my usb gadget to a specific string, but I simply can't find a way to make configfs accept this.
> >
> > When I set my gadget up on my Beaglebone Black (uname -a: Linux beaglebone 4.14.108-ti-r113 #1 SMP PREEMPT Wed Jul 31 00:01:10 UTC 2019 armv7l GNU/Linux).
> >
> > I get (output from lsusb):
> >
> > iInterface 5 HID Interface
> >
> >
> > But I want it to be something like:
> >
> > iInterface 4 LPC-LINK2 CMSIS-DAP V5.224
> >
> >
> > This seems to be wired up as a fixed value in f_hid.c and doesn't seem to have a corresponding way to actually change it via configfs.
> >
> >
> > #define CT_FUNC_HID_IDX 0
> >
> > static struct usb_string ct_func_string_defs[] = {
> > [CT_FUNC_HID_IDX].s = "HID Interface",
> > {}, /* end of list */
> > };
Then maybe you need to fix f_hid.c. Or maybe configfs isn't meant to
allow the user to specify these string index values (I don't know any
of the configfs details).
Alan Stern
next prev parent reply other threads:[~2020-01-15 15:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 23:58 Unable to set "iInterface" in usb gadget via configfs Andrew P. Lentvorski
2020-01-15 15:14 ` Alan Stern [this message]
2020-01-16 2:23 ` Andrew P. Lentvorski
2020-01-16 13:02 ` Felipe Balbi
2020-01-17 0:39 ` Andrew P. Lentvorski
2020-01-17 9:25 ` Felipe Balbi
2020-01-18 0:58 ` Andrew P. Lentvorski
2020-01-19 16:45 ` Felipe Balbi
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=Pine.LNX.4.44L0.2001151011520.1788-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=bsder@allcaps.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;
as well as URLs for NNTP newsgroup(s).