All of
 help / color / mirror / Atom feed
From: Michal Nazarewicz <>
To: Krzysztof Opasiak <>
	Andrzej Pietrasiewicz
	'Manu Gautam' <>,
	Karol Lewandowski
	Marek Szyprowski
Subject: Re: [PATCHv2] usb: gadget: f_fs: Add flags to descriptors block
Date: Wed, 04 Jun 2014 21:06:20 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <005901cf8000$c16ec090$444c41b0$>

>> -struct usb_functionfs_descs_head {
>> -	__le32 magic;
>> -	__le32 length;
>> -	__le32 fs_count;
>> -	__le32 hs_count;
>> -} __attribute__((packed));

On Wed, Jun 04 2014, Krzysztof Opasiak <> wrote:
> I have tried to compile FFS examples with v3.15-rc8 but I have faced an
> issue that they are unable to build due to missing definition of this
> structure.

> The same is with adb, sdb and all userspace apps which use legacy
> API. What is the reason of removing it? Was your intentions?

It was a mistake on my part.

> Maybe would be a good idea to leave this structure untouched as legacy
> userspace API?

I don't care either way to be honest.  I guess if there's non-negligible
number of usb_functionfs_descs_head structure users out there, I can
prepare a CL adding the structure back.

> There is also no structure definition for new API, maybe suitable
> structure should be defined (struct usb_functionfs_descs_head2 for
> example) to make userspace life easier?

That structure would not have many fields though, since what exactly the
header contains depends on the flags.  Whether fs_count, hs_count and
ss_count fields are present depends on which bits in the flags are set.
So the usb_functionfs_descs_head2 structure could only contain:

	struct usb_functionfs_descs_head2 {
		__le32 magic;
		__le32 length;
		__le32 flags;

I'm not sure if that would be particularly helpful.

Best regards,                                         _     _
.o. | Liege of Serenely Enlightened Majesty of      o' \,=./ `o
..o | Computer Science,  Michał “mina86” Nazarewicz    (o o)
ooo +--<>--<xmpp:mina86-/>--ooO--(_)--Ooo--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to
More majordomo info at

  parent reply	other threads:[~2014-06-04 19:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-24  9:30 [PATCH v5 1/1] usb: gadget: f_fs: Add support for SuperSpeed Mode Manu Gautam
     [not found] ` <>
2014-02-25  4:47   ` Manu Gautam
2014-02-25 14:01 ` [RFC] usb: gadget: f_fs: Add flags to descriptors block Michal Nazarewicz
     [not found]   ` <>
2014-02-25 17:02     ` [PATCHv2] " Michal Nazarewicz
2014-02-25 18:32       ` Felipe Balbi
2014-02-28 10:11       ` Manu Gautam
     [not found]       ` <>
2014-06-04 14:24         ` Krzysztof Opasiak
     [not found]           ` <005901cf8000$c16ec090$444c41b0$>
2014-06-04 19:06             ` Michal Nazarewicz [this message]
2014-06-05 11:32               ` Krzysztof Opasiak

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.